Feature Incomplete - Custom DHCP Options Do Not Work
I am getting increasingly frustrated with the lack of DHCP support on a business grade router/controller
ER605V2 2.2.4
OC200V1 1.31.3 (current latest)
You don't support Next-Server 67 used for PXE boot
- My thread from last year - DHCP next server is there on controller 5.15 - https://community.tp-link.com/en/business/forum/topic/708490
- "Release Q3 2024" cited from thread created two years ago - https://community.tp-link.com/en/business/forum/topic/641862
You don't support 119 Search Domains
- Thread by @ContraVarus https://community.tp-link.com/en/home/forum/topic/712982
And despite introducing "Custom DHCP Options" in Omada Cloud Controller with the options of "String", "IP Address", and "HEX" we are still no closer to solving the above.
Testing
Custom Option 119 - String - 'hello.test'
NMAP | broadcast-dhcp-discover: | Response 1 of 1: | Interface: eth0 | IP Offered: 192.168.30.166 | DHCP Message Type: DHCPOFFER | Server Identifier: 192.168.30.1 | IP Address Lease Time: 2h00m00s | Renewal Time Value: 1h00m00s | Rebinding Time Value: 1h45m00s | Subnet Mask: 255.255.255.0 | Broadcast Address: 192.168.30.255 | Router: 192.168.30.1 | Domain Name: lan |_ Domain Name Server: 192.168.30.10 TCPDUMP 192.168.30.1.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, length 309, xid 0x171b39f5, Flags [Broadcast] (0x8000) Your-IP 192.168.30.166 Server-IP 192.168.30.1 Client-Ethernet-Address de:ad:c0:de:ca:fe Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message (53), length 1: Offer Server-ID (54), length 4: 192.168.30.1 Lease-Time (51), length 4: 7200 RN (58), length 4: 3600 RB (59), length 4: 6300 Subnet-Mask (1), length 4: 255.255.255.0 BR (28), length 4: 192.168.30.255 Default-Gateway (3), length 4: 192.168.30.1 Domain-Name (15), length 3: "lan" Domain-Name-Server (6), length 4: 192.168.30.10 END (255), length 0
Nope, no option 119
Custom Option 119 - HEX - 05:68:65:6C:6C:6F:04:74:65:73:74:00 (aka 'hello.test')
NMAP Pre-scan script results: | broadcast-dhcp-discover: | Response 1 of 1: | Interface: eth0 | IP Offered: 192.168.30.166 | DHCP Message Type: DHCPOFFER | Server Identifier: 192.168.30.1 | IP Address Lease Time: 2h00m00s | Renewal Time Value: 1h00m00s | Rebinding Time Value: 1h45m00s | Subnet Mask: 255.255.255.0 | Broadcast Address: 192.168.30.255 | Router: 192.168.30.1 | Domain Name: lan |_ Domain Name Server: 192.168.30.10 TCPDUMP
192.168.30.1.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x63b4e05f, Flags [Broadcast] (0x8000) Your-IP 192.168.30.166 Server-IP 192.168.30.1 Client-Ethernet-Address de:ad:c0:de:ca:fe Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message (53), length 1: Offer Server-ID (54), length 4: 192.168.30.1 Lease-Time (51), length 4: 7200 RN (58), length 4: 3600 RB (59), length 4: 6300 Subnet-Mask (1), length 4: 255.255.255.0 BR (28), length 4: 192.168.30.255 Default-Gateway (3), length 4: 192.168.30.1 Domain-Name (15), length 3: "lan" Domain-Name-Server (6), length 4: 192.168.30.10 END (255), length 0 PAD (0), length 0, occurs 3
Nope, no option 119
I did the exact same testing on DCHP Option 224 with the same result.
Why are Custom DCHP options being silently dropped?
What is it?
Tell me my testing methodology is wrong, tell me I'm incorrect. I don't mind I just want the features to work. Get me on with a technical engineer to demonstrate the working features on DHCP options! I welcome it!
Tell me your custom DHCP option is feature incomplete and your developers are actively working on resolving the dummy front-end to poor code.
Or tell me you are taking your customers for a ride and promising features for business grade equipment - like is standard for shotty pre-sales - just to get sales.
---
Other threads have been dismissive with "just buy another device that meets your needs". That answer is not satisfactory in an ecosystem where people have bought in and expect standard business grade networking options to be present.