How to configure DHCP VLAN Relay on L2 Managed switches using the new GUI

T1600G-18TS( V2 ) , T1600G-28TS( V3 ) , T2600G-28MPS( V3 ) , T1600G-52PS( V3 ) , T2600G-52TS( V3 ) , T1600G-52TS( V3 ) , T2600G-28TS( V3 ) , T2600G-28SQ( V1 ) , T1600G-28PS( V3 ) , T1700X-16TS( V3 )
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device, and check either the Datasheet or the firmware section for the latest improvements added to your product. Please note that product availability varies by region, and certain models may not be available in your region.
This article applies to:
T1600G-52TS v3 or above, T1600G-52PS v3 or above, T1600G-28PS v3 or above, T1600G-28TS v3 or above, T1600G-18TS v2 or above, T1700X-16TS v3 or above, T2600G-52TS v3 or above, T2600G-28TS v3 or above, T2600G-28MPS v3 or above, T2600G-28SQ v1 or above.
Generally, if a client needs to get an IP address from the DHCP server, they should be in a same subnet, because the DHCP packet transmission is restricted in a LAN. This mechanism may bring inconvenience when the administrator needs to assign IP addresses to clients in different subnets. Because under normal circumstances, he has to deploy one DHCP server for each subnet, which is inconvenient and uneconomical.
You can configure DHCP Relay to solve this problem. Through DHCP Relay, you can just deploy one DHCP server and this server can offer IP addresses to clients in different subnets or VLANs.
DHCP Relay includes DHCP Interface Relay and DHCP VLAN Relay.
DHCP Interface Relay:
DHCP Interface Relay can be applied in such scenario: a DHCP server is deployed to offer IP addresses to clients in multiple subnets. These subnets all have their own Layer 3 gateway (L3 Interface or VLAN Interface).
With DHCP Interface Relay enabled, when the switch receives the DHCP request packets, it will forward the packets through the Layer 3 gateway to the DHCP server, and forward the DHCP offers from the DHCP server to the corresponding subnets afterwards. The DHCP server will determine which IP address of subnet should be assigned to the clients based on the Layer 3 gateway.
DHCP VLAN Relay:
DHCP VLAN Relay can be applied in such scenario: a DHCP server is deployed to offer IP addresses to clients in multiple VLANs. These VLANs do not have VLAN interfaces.
DHCP VLAN Relay can manually designate an L3 interface for all the VLANs as the default relay agent interface. All the DHCP packets can be forwarded through this interface so that the clients can get IP addresses from the DHCP server.
Here we use an example to introduce the configurations of DHCP VLAN Relay.
PC 1 and PC 2 are in different VLANs, both of the VLANs have no VLAN interfaces. Now the administrator deploys one DHCP server on the network, and want the server to assign IP addresses to PC 1 and PC 2.
Configuration Scheme
In the given situation, the DHCP server and the computers are isolated in different network segments, so the DHCP request from the clients cannot be directly forwarded to the DHCP server. Considering that the two VLANs have no Layer 3 gateways, we recommend you to configure DHCP VLAN Relay to satisfy the requirement.
In this example, the DHCP server is demonstrated with T2600G-52TS and the DHCP relay agent is demonstrated with T2600G-28TS. We will show you the configurations on both DHCP server and DHCP relay agent.
Configuring DHCP Server
- Go to L3 FEATURES > DHCP Service > DHCP Server > DHCP Server page, enable DHCP server globally.
- Go to L3 FEATURES > DHCP Service > DHCP Server > Pool Setting page, create one DHCP IP pool for both VLAN 10 and VLAN 20 in 192.168.0.0/24 subnet..
Note: For DHCP VLAN Relay, the DHCP server will assign IP addresses of the same subnet to both VLAN 10 and VLAN 20, although the clients belong to different VLANs. The subnet of the addresses to be assigned is determined by the subnet that the default relay agent interface is in, so here we can create only one DHCP pool in 192.168.0.0/24 subnet for both VLAN 10 and VLAN 20.
Configuring VLAN on DHCP Relay Agent
- Go to L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config page, create VLAN 10 and VLAN 20. Add the corresponding ports to the VLAN.
- Go to L2 FEATURES > VLAN > 802.1Q VLAN > Port Config page, set the PVID of port 1/0/1 as 10 and 20 of port 1/0/2.
Configuring DHCP VLAN Relay on DHCP Relay Agent
- Go to L3 FEATURES > DHCP Service > DHCP Relay > DHCP Relay Config page, enable DHCP Relay feature globally.
- Go to L3 FEATURES > DHCP Service > DHCP Relay > DHCP VLAN Relay page, in the Default Relay Agent Interface section, specify VLAN interface 1 (the default management VLAN interface ) as the default relay agent interface.
- Go to L3 FEATURES > DHCP Service > DHCP Relay > DHCP VLAN Relay page, click
to specify the server address for the clients in VLAN 10 and VLAN 20.
Now, all the configurations are finished.
For the detailed introduction of the related functions, you can also refer to the User Guides of the corresponding functions:
Configuring DHCP Service at: https://www.tp-link.com/us/configuration-guides/configuring_dhcp_t1600g_t2600g/
Configuring 802.1Q VLAN at: https://www.tp-link.com/us/configuration-guides/configuring_802_1q_vlan/
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.

TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or