So ... still no Option 66 and 67 on ER605?
Edit: Standalone (not connected to Omada Controller. Another can of worms - a lot of features are lost on association)
All threads on the matter are locked:
https://community.tp-link.com/en/business/forum/topic/641862
What is the status on DHCP Options 66 and 67 and next-server?
The most relevant information was "Release Q3 2024"
I spent hours trying to get what seemed like a basic feature working but was met with forums stating it wasn't possble on a business-grade router.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @NWer
Thanks for posting in our business forum.
NWer wrote
@Order66 I'm in need of this as well.
It didn't take long to find 3-year-old threads about the missing options.Unfortunately, it seems like they didn't fix this all this time.
How does it come that such a big company isn't able to roll out a crucial business function to their business line-up in years?
Please TP-Link, make this happen...
It is kinda ignorant to mess up the DHCP option number to its name.
Have you looked at the DHCP option where you have DHCP TFTP and DHCP Network Boot?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@KimcheeGUN I guess so.
Not familiar with the term but going for NIC boot/PXE boot to a linux host and linux based OS ISO
- Copy Link
- Report Inappropriate Content
@Order66 I'm in need of this as well.
It didn't take long to find 3-year-old threads about the missing options.
Unfortunately, it seems like they didn't fix this all this time.
How does it come that such a big company isn't able to roll out a crucial business function to their business line-up in years?
Please TP-Link, make this happen...
- Copy Link
- Report Inappropriate Content
Hi @NWer
Thanks for posting in our business forum.
NWer wrote
@Order66 I'm in need of this as well.
It didn't take long to find 3-year-old threads about the missing options.Unfortunately, it seems like they didn't fix this all this time.
How does it come that such a big company isn't able to roll out a crucial business function to their business line-up in years?
Please TP-Link, make this happen...
It is kinda ignorant to mess up the DHCP option number to its name.
Have you looked at the DHCP option where you have DHCP TFTP and DHCP Network Boot?
- Copy Link
- Report Inappropriate Content
@Clive_A
Solution you say?
Also accusing customers of ignorance isn't a very nice move but anyways.
I'm not running in standalone mode, like everyone else using more than 3 devices probably is.
Yes, forgot to mention but it won't change my outcome.
It isn't possible - or am I wrong?
Option 66 is there but can't be used for PXE since with missing option 67 I can't send the boot file name.
Now tell me how ignorant I am...
- Copy Link
- Report Inappropriate Content
Hi @NWer
Thanks for posting in our business forum.
NWer wrote
@Clive_A
Solution you say?Also accusing customers of ignorance isn't a very nice move but anyways.
I'm not running in standalone mode, like everyone else using more than 3 devices probably is.Yes, forgot to mention but it won't change my outcome.
It isn't possible - or am I wrong?
Option 66 is there but can't be used for PXE since with missing option 67 I can't send the boot file name.Now tell me how ignorant I am...
What model and firmware do you use? Have you made sure they are on the latest firmware?
I am seeing them on ER707-M2 and ER8411 standalone and controller mode with V5.14. Same for ER605 V2 2.2.6. All latest firmware.
And you are offered the custom DHCP option if you say there are none 66 and 67.
What you might miss is the Next Server. Have you confirmed it or confirmed what's missing to make it work?
Even if we need to optimize the firmware, a line of "make it happen" does not make sense without knowing what firmware and model you have.
As the senior member Kim replied, he got it working fine but not you. You have examined the steps before popping up a question, is that true?
- Copy Link
- Report Inappropriate Content
What model and firmware do you use? Have you made sure they are on the latest firmware?
I'm currently on the following setup:
TL-R605 v1.0 - 1.3.1 Build 20231207 Rel.61384
On containerized Controller - 5.14.32.4
What you might miss is the Next Server. Have you confirmed it or confirmed what's missing to make it work?
I get offered option 66 but not 67, which I need to boot my clients from the network.
You have examined the steps before popping up a question, is that true?
Yes, I have. In your screenshot in Standalone Mode, there clearly is the option I need, but not in my managed setup.
Instead of Kim, I'm not using SCCM, I can't tell if option 66 is enough for this use case but in my scenario, I have to send the BootFileName to the client, which is done by option 67.
- Copy Link
- Report Inappropriate Content
Hi @NWer
Thanks for posting in our business forum.
NWer wrote
What model and firmware do you use? Have you made sure they are on the latest firmware?
I'm currently on the following setup:
TL-R605 v1.0 - 1.3.1 Build 20231207 Rel.61384
On containerized Controller - 5.14.32.4
What you might miss is the Next Server. Have you confirmed it or confirmed what's missing to make it work?
I get offered option 66 but not 67, which I need to boot my clients from the network.
You have examined the steps before popping up a question, is that true?
Yes, I have. In your screenshot in Standalone Mode, there clearly is the option I need, but not in my managed setup.
Instead of Kim, I'm not using SCCM, I can't tell if option 66 is enough for this use case but in my scenario, I have to send the BootFileName to the client, which is done by option 67.
ER605 V1 is EOL. 1.3.1 is the last firmware it has. We continue to update the firmware with the security fixes but without any new features.
Even if it is DHCP 66 and 67, you might need next server which is the case we used to see. 3 makes a full solution.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 372
Replies: 8
Voters 0
No one has voted for it yet.