Option 66 does not get passed on to dhcp clients.
Option 66 does not get passed on to dhcp clients.
I'm unable to get network booting to work. Option 66 doesn't seem to be passed on to the clients.
I've tested with netbootxyz and iVentoy. Using both HyperV and Virtualbox as machines to test against.
They all try to connect to the gateway IP instead of the IP specified in option 66. Option 67 is passed on as expected.
Any suggestions?
Controller: 5.12.7 hosted on Ubuntu 22.04.3
Router: ER605 V2 - Firmware 2.2.2
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi Bob and dewk,
Clive_A wrote
Thanks for posting in our business forum.
Confirmed w/ the dev that there will be a beta for standalone to have the next server. If you are using a controller, please let me know the controller version.
Here's the beta firmware for you. Please download the QR code and run a scan of it.
It adds support to the next server in standalone mode. For anyone who uses a controller, this might not be as helpful. Please wait for the future firmware of the Omada Controller.
Please note that this download link will expire within 7 days.
- Copy Link
- Report Inappropriate Content
I noticed when I was configuring my Omada router against Windows MDT/SCCM server. Even though the IP was right, and the file name was wrong, it bombed out like it wasn't passing the IP. Eventually I got it to work.
Are you sure the filename is right?
- Copy Link
- Report Inappropriate Content
Thanks for your suggestion.
I can confirm that the filename is correct, I just tried downloading the file from the server with a TFTP client and that worked.
- Copy Link
- Report Inappropriate Content
@dewk Same issue
Showing same issue.
Even tried using the dnsmasq setting for proxy. I did get it to boot but the Next-Server still shows Router IP and only the DHCP Proxy Next-Server is listed as the TFTP server.
I did try Option 66 and/or Option 150 on the ER7206 to no avail. Latest firmware posted.
My ER7206
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
bob0builder wrote
@dewk Same issue
Showing same issue.
Even tried using the dnsmasq setting for proxy. I did get it to boot but the Next-Server still shows Router IP and only the DHCP Proxy Next-Server is listed as the TFTP server.
I did try Option 66 and/or Option 150 on the ER7206 to no avail. Latest firmware posted.
My ER7206
Any luck with the Wireshark monitoring the DHCP request?
Connect a new laptop or computer to the router, there will be a DHCP request, easy to catch the DHCP interaction.
New laptop with Wireshark installed. Start to capture on the right NIC. Filter dhcp. And see if the DHCP option 66 is there.
BTW, you can also try the 2.1.5 beta. Early Access ER605 V2_2.1.5 Build 20231024 Beta Firmware for Omada Controller V5.11 (Released on Oct 26th, 2023)
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
Thanks for your help and input.
It seems like the ip for the TFTP server is included as per wireshark monitor.
If I do a DHCP request via nmap it includes \x00 at the end of the TFTP server IP, I do not not know if this is significant.
Either way, it's not working for me with physical computers or VM's.
I will try the 2.1.5 beta during the weekend and report back.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
Same behavior on the 2.1.5 beta. Early Access ER605 V2_2.1.5 Build 20231024 Beta Firmware.
- Copy Link
- Report Inappropriate Content
Hi @dewk
Thanks for posting in our business forum.
dewk wrote
Hi @Clive_A
Same behavior on the 2.1.5 beta. Early Access ER605 V2_2.1.5 Build 20231024 Beta Firmware.
Then I guess it is your device. The DHCP packet from the DHCP server contains the TFTP (Option 66), so you should search this on the system forum.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A,
I did some troubleshooting and it seems like I need next-server to be set in the DHCP header for netboot xyz, not option 66.
The boot file can be specified in either header or option 67.
Succesful test setup with minimal config on ISC DHCP server.
ISC config:
ISC DHCP Offer:
ER605 Offer for comparison:
Any chance we can set next-server and boot file name in the DHCP header instead of using options on Omada?
- Copy Link
- Report Inappropriate Content
Hi @dewk
Thanks for posting in our business forum.
dewk wrote
Hi @Clive_A,
I did some troubleshooting and it seems like I need next-server to be set in the DHCP header for netboot xyz, not option 66.
The boot file can be specified in either header or option 67.
Succesful test setup with minimal config on ISC DHCP server.
ISC config:
ISC DHCP Offer:
ER605 Offer for comparison:
Any chance we can set next-server and boot file name in the DHCP header instead of using options on Omada?
Got some news from the dev and senior engineer that the next server option is missing on this firmware. Will provide a beta(based on V2.2.2 firmware) soon.
I will let you know the download link as soon as I am updated.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 3938
Replies: 20