Option 66 does not get passed on to dhcp clients.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Option 66 does not get passed on to dhcp clients.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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
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.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @dewk
Thanks for posting in our business forum.
dewk wrote
The beta will only apply to the standalone mode. I am collecting the controller version for the dev team. So, when the beta is ready, you need to turn the device into standalone mode. (Forgetting the device will reset the device. Please proceed at your own discretion.)
- Copy Link
- 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
- Copy Link
- Report Inappropriate Content
I can confirm that it works. Thanks for the great support.
Now I'll just have to wait for the Omada update.
- Copy Link
- Report Inappropriate Content
@dewk Thanks for helping support get to the bottom of this issue. I just came across this behavior 2 nights ago and was scratching my head. Even had to dust off the Wireshark skills (or lack there of!) and refer to the RFC just to work out that I wasn't doing something wrong.
I am also looking forward to this being fixed in the Omada Hardware Controller as I don't have any desire to run the standalone firmware on the ER605.
Not sure if we'll get an ETA for when this may be available, but that'd be nice :-)
Kind regards
----
Router: ER605 V2 - Firmware 2.1.2
Omada Controller - Version: 5.12.9 Build: 2.11.3 Build 20230906 Rel.36272
- Copy Link
- Report Inappropriate Content
@dewk Can we confirm this is an issue with the ER7206 as well? After testing I appear to have the same issue of it showing the default gateway instead of the tftp server.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I agree. I just spent countless hours investigating all the wrong things (AND bought a new ER8411), only to learn Option 66 doesn't work in the controller (version 5.13.30.8).
I couldn't be more upset.
What do I do now? Switch the ER8411 & the SX3008F to standalone mode, rebuild the entire network & cross my fingers Option 66 works?
PLEASE help
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 3612
Replies: 20
Voters 1
