How to correctly configure Option 66 and 67 in Omada?
How to configure Option 66 and 67 in Omada (with OC200).
I have an iVentoy pxe server running on a Linux server. I followed the all iVentoy's documentation stated in iVentoy's website
but I can't get it to work in Omada.
The detected PXE server is still my gateway instead of the IP address of my Linux machine running iVentoy.
These are the settings:
And this was the error:
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @ceejaybassist
Thanks for posting in our business forum.
You might need the next server over them. Next server is quite important for PXE boot. Standalone mode has a beta but not for the controller. Controller is ETA V5.15 or 5.16 to have this added.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A,
Over a yeas has passed ant there is still no 5.15 release. Any ETA available so PXEboot will work in controller-mode?
- Copy Link
- Report Inappropriate Content

Hi @XisoP_
Thanks for posting in our business forum.
XisoP_ wrote
Hi @Clive_A,
Over a yeas has passed ant there is still no 5.15 release. Any ETA available so PXEboot will work in controller-mode?
1. We have a list of requests pending to be added. They have been marked with different priorities. From last year the very first request, till it was officially reported and evaluated and considered to be added to the V5.15.X release early this year.
2. Please note that this will involve an adapted firmware, not just a controller update. Firmware development is a complex process, and timelines may change. Therefore, we cannot provide a specific release date at this time. Please stay tuned to future firmware release notes for updates.
So it is not just added to the firmware that easy. I probably can apply for a beta for you but you cannot use it in the controller mode until the controller is fully adapted.
3. Due to the previous posts of feature requests, it had an unpleasant conversation. We no longer provide specific ETA, or timeline now. Please wait for the firmware release and refer to the release note.
- Copy Link
- Report Inappropriate Content
I got a couple of:
ER605 v2.0 2.2.6 Build 20240718 Rel.82712
Still no updated that support this, no timeline or ETA?
And if you comment it will be delete?
Also when i bought it dhcp 66 function was fully supported. According to your specs.
So is it a scam? or are you hoping to get it out there with in a 5 years? or hoping people stop asking about it? what's the plan?
Just made a ticket for a return of 180k in euro's, because this function isn't working and if you replay to a topic it will be deleted.
ps. I got it screenshot and will use it as proof of fraud if it is removed again
- Copy Link
- Report Inappropriate Content

Hi @Cookie_050
Cookie_050 wrote
I got a couple of:
ER605 v2.0 2.2.6 Build 20240718 Rel.82712
Still no updated that support this, no timeline or ETA?
And if you comment it will be delete?
Also when i bought it dhcp 66 function was fully supported. According to your specs.
So is it a scam? or are you hoping to get it out there with in a 5 years? or hoping people stop asking about it? what's the plan?
Just made a ticket for a return of 180k in euro's, because this function isn't working and if you replay to a topic it will be deleted.
ps. I got it screenshot and will use it as proof of fraud if it is removed again
If you placed a bulk order, contact the local TP-Link sales team regarding your customized firmware.
If you feel this product cannot meet your expectations, please return it in time before the return window closes.
Something wrong with the reply system. I don't know what the web team has changed. It is not normal recently.
The reply system has been patched.
- Copy Link
- Report Inappropriate Content
maybe it helps someone, it's dirty but it works.
Option 67: tftp://<ip of tftp server>/<file>.ipxe
And for option 66 nothing.
- Copy Link
- Report Inappropriate Content

Hi @Cookie_050
Thanks for posting in our business forum.
Cookie_050 wrote
maybe it helps someone, it's dirty but it works.
Option 67: tftp://<ip of tftp server>/<file>.ipxe
And for option 66 nothing.
Cool. But I don't have the environment for this test.
I recall some people saying that 66 and 67 are not enough for a bootup.
Most complaints are about the next server. 66 and 67, with the next server, will form a proper bootup. We have long supported the 66 and 67 but they still report that this isn't working. I believe the perp is the next server.
That's also the reason why we have customized firmware to implement the next server. We are aware of this and the team will work on with the related features.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1217
Replies: 7
Voters 0
No one has voted for it yet.