Hello,

I would like to submit a technical feature request regarding DHCP Relay (IP Helper) functionality on TP‑Link switches.

Currently, TP‑Link switches only permit the configuration of a single DHCP Relay address per VLAN interface. This limitation creates operational constraints in environments where DHCP services and PXE/WDS services are intentionally separated across different servers for architectural or security reasons.

In our environment, Microsoft DHCP is hosted independently from the PXE/WDS infrastructure. As per Microsoft’s official guidance, DHCP Options 66/67 should not be used for PXE redirection, and IP Helpers are the recommended method for forwarding PXE broadcast traffic to the appropriate server.
Reference: https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/os-deployment/boot-from-pxe-server

Because TP‑Link supports only one IP Helper, DHCP Discover and PXE boot requests cannot be forwarded simultaneously to both servers. As a workaround, I am having to currently combine DHCP and WDS on the same host server, which is not ideal and deviates from recommended network design practices. Other vendors (e.g., Ubiquiti, Cisco, HPE) typically support multiple DHCP Relay targets per VLAN interface, allowing DHCP and PXE/WDS to remain logically and physically separated.

Feature request:

• Increase the number of supported DHCP Relay (IP Helper) addresses per VLAN interface from one to at least two, or ideally remove the limit entirely.
• This enhancement should apply across all TP‑Link managed switch product lines to support more flexible and standards‑aligned network architectures.

Implementing this functionality would enable proper forwarding of DHCP and PXE/WDS traffic in multi‑server environments without requiring unnecessary service consolidation.

Thank you,
Ben