PXE Boot Bug
I have been waiting for option 66 and option 67 for a while to test in my homelab pxe boot. I am not 100% certain if the issue is on my end of the configuration given PXE boot is new to me. Maybe there is a bug in the beta firmware so I am asking for help.
This network (VLAN 10) is 192.168.10.0/24 and the PXE server is at 192.168.10.5. I am testing with a VM and changing option 67 parameters are catch properly during the PXE boot sequence although option 66 does not seems to work (always point back to my gateway ip = 192.168.10.1).
Is this a bug or I am not understanding how option 66-67 are expected to work ?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @Irish1986,
Irish1986 wrote
I am testing with a VM and changing option 67 parameters are catch properly during the PXE boot sequence although option 66 does not seems to work (always point back to my gateway ip = 192.168.10.1).
Yes, it is normal that it always points back to the Gateway IP, because the controller doesn't support to set of Next Server IP addresses at present.
This has already been forwarded to the TP-Link team for evaluation.
Thanks for your valuable feedback!
- Copy Link
- Report Inappropriate Content
Hello @Irish1986,
Irish1986 wrote
I am testing with a VM and changing option 67 parameters are catch properly during the PXE boot sequence although option 66 does not seems to work (always point back to my gateway ip = 192.168.10.1).
Yes, it is normal that it always points back to the Gateway IP, because the controller doesn't support to set of Next Server IP addresses at present.
This has already been forwarded to the TP-Link team for evaluation.
Thanks for your valuable feedback!
- Copy Link
- Report Inappropriate Content
Any update on this? What is the solution moving forward for next server IP for pxe boot server?
- Copy Link
- Report Inappropriate Content
Which router and firmware version are you using? I'm using a 7206 on the latest release and PXE Boot works for me with WIndows SCCM.
Also on the latest controller version for a OC200.
- Copy Link
- Report Inappropriate Content
Model: OC200
Hardware Version: V1
Firmware Version: V5.9.32
I am trying with a linux guest agent and it still not working for me. The "next server IP" is not being past to, it should not be 192.168.10.1 but rather 192.168.10.5. I've tried a few time by either updating or reboot after applying those changes.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
did you ever get this to work? I've been trying to fix it for a while.
- Copy Link
- Report Inappropriate Content
Nope I've posted in the origin Features & Request thread while back and no update. I am still waiting for an update but with the current issue debacle update I've been waiting patiently.
- Copy Link
- Report Inappropriate Content
I have PXE boot working on Windows MDT/SCCM server with my 7206 on the latest beta firmware.
IDK if this is a bug with the Linux imaging server abd TPLink router combo setup.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 947
Replies: 10
Voters 0
No one has voted for it yet.