Business Community > Controllers > PXE Boot Bug
< Controllers

PXE Boot Bug

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

PXE Boot Bug

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
PXE Boot Bug
PXE Boot Bug
2023-04-10 19:18:45 - last edited 2023-11-30 08:05:55
Tags: #Firmware Update #pxe boot
Model: OC200  
Hardware Version: V1
Firmware Version: V5.9.32

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 ?

 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:PXE Boot Bug-Solution
2023-04-11 03:09:25 - last edited 2023-11-30 08:05:55

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!

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  1  
  1  
#2
Options
10 Reply
Re:PXE Boot Bug-Solution
2023-04-11 03:09:25 - last edited 2023-11-30 08:05:55

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!

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  1  
  1  
#2
Options
Re:PXE Boot Bug
2023-06-02 22:59:44

  @Hank21 

 

Any update on this? What is the solution moving forward for next server IP for pxe boot server? 

  1  
  1  
#3
Options
Re:PXE Boot Bug
2023-06-05 12:24:15

  @Irish1986 

 

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.

 

 

 

 

I can not teach anyone anything - I can only make them think - Socrates
  0  
  0  
#4
Options
Re:PXE Boot Bug
2023-06-09 18:01:01

 

  @KimcheeGUN 

 

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.

 

  0  
  0  
#5
Options
Re:PXE Boot Bug
2023-06-11 18:41:05

  @Irish1986 

 

Did I miss the firmware of the 7206, that you were using?

I can not teach anyone anything - I can only make them think - Socrates
  0  
  0  
#6
Options
Re:PXE Boot Bug
2023-06-13 00:50:54

Info  @KimcheeGUN 

  1  
  1  
#7
Options
Re:PXE Boot Bug
2023-07-20 21:51:28

 

did you ever get this to work? I've been trying to fix it for a while. 
 

 

 

  0  
  0  
#8
Options
Re:PXE Boot Bug
2023-07-20 22:39:02

  @Liev 

 

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. 

  0  
  0  
#9
Options
Re:PXE Boot Bug
2023-07-21 12:27:22 - last edited 2023-07-21 12:27:59

  @Liev 

 

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.  

I can not teach anyone anything - I can only make them think - Socrates
  0  
  0  
#10
Options
Re:PXE Boot Bug
2023-11-25 05:12:23
I have tried network booting on Linux and windows. I always get the gateway IP instead of the network boot IP. I am able to set the filename that it looks for, and it is showing that without problem.
  0  
  0  
#11
Options

Information

Helpful: 0

Views: 1585

Replies: 10

Tags

Firmware Update
pxe boot
Related Articles
ER605 V2 - PXE Boot not working?
5577 0
 PXE Boot on different VLAN
773 0
 PXE Boot is not working on Jetstream SG3428X v1.30
130 0
OC300_v1 version mismatch / bug?
503 0
 Autostart / Start on boot / Run at startup bug
283 0
There is a BUG :D ..... Screenshot - Insights.
612 1
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.