How to configure the DHCP Relay in TP-Link Switch
T1600G-28TS , T3700G-52TQ , T1700G-28TQ , T2600G-52TS , T2600G-18TS , T2600G-28TS , T1600G-28PS , T2700G-28TQ , T2600G-28MPS( V1 V2 V3 ) , T1600G-52PS , T1600G-52TS , T3700G-28TQ , T1700X-16TS
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.
Generally, the clients get IP by broadcasting the DHCP packets in the LAN, and the server will response clients’ request. As this way, it is necessary to keep the DHCP server and clients in the same LAN. When you need more than one DHCP subnets, you will need more than one DHCP server in the same LAN with each subnets which could increase the cost of network and is hard to manage.
The function of DHCP Relay is used to solve this problem. It can transmit different subnets’ DHCP packets. So all the subnets can share the same DHCP server. Then how to configure the DHCP Relay in TP-Link Switch? Here is the guide.
Topology:
We need a DHCP server which can allocate more than one subnets. Here we take a L2+ switch of TP-Link, T2600G-28TS as the DHCP server. And another switch T1600G-28TS takes the part of DHCP Relay. We plan to give two different subnets to the clients connected to the T1600G-28TS, 192.168.10.0/24 and 192.168.20.0/24. So this is the real topology below:
Equipment: T2600G-28TS, T1600G-28TS, PCs
Topology Introduction: The T2600G-28TS is DHCP server which connected to the T1600G-28TS by the port 1/0/2; the client are divided into two different VLANs: VLAN10 and VLAN20. VLAN10 includes the port 1/0/4, 1/0/6, 1/0/8 while the VALN20 includes port 1/0/3, 1/0/5, 1/0/7.
Step 1:
Login the T2600G-28TS, enable DHCP server and set up two IP Address Pools.
Follow the Routing >> DHCP Server >> DHCP Server, then enable it.
Follow the Routing >> DHCP Server >> Pool Setting, input the Network Address, also the Subnet Mask. Lease Time and Default Gateway are needed. Then click Create.
Follow the same step above and set another IP Address Pool. You will get two IP Address Pools on the pool table.
Note: The reason we take T2600G-28TS as the DHCP server is it can allocate different subnets, that’s what we need to show how the DHCP Relay work.
Step 2:
Create a Static Routing in the T2600G-28TS. A static routing is used to tell the T2600G-28TS how to send the packets back to the clients.
Follow the Routing >> Static Routing. Input the Destination subnet and Subnet Mask. Here we set the 192.168.0.10 as the Next Hop of the routing, because it is the interface of the T1600G-28TS.
There are two subnets, so there should have two static routes in the table.
Till now, the configuration on the DHCP Server is over.
Step 3:
First step of the setting in T1600G-28TS is giving it another Interface, because it was conflict with the one in T2600G-28TS (192.168.0.1).
Follow the Routing >> Interface. Change the interface of VLAN1 to 192.168.0.10.
After that, we will be able to login the switch by the IP 192.168.0.10.
Step 4:
Then, the different subnets should be divided into different VLANs, so we need to create two VLANs. As we planned before, we add port 1/0/4, 1/0/6, 1/0/8 in VLAN10, and port 1/0/3, 1/0/5, 1/0/7 in VLAN20. The uplink port 1/0/2 should be added into each VLANs.
Note: When we add ports to the VLANs, as default, the PVID of the ports are 1. To make the date transmit into their own VLAN. It is needed to change the PVID of port 1/0/4, 1/0/6, 1/0/8 to 10, while the PVID of port 1/0/3, 1/0/5, 1/0/7 to 20 manually.
Step 5:
After create VLANs, we should configure the Interface for each VLANs. The same step as setting for the VALN1 Interface, like 192.168.10.1 for VLAN10.
Step 6:
Enable the DHCP Relay. Follow the Routing >> DHCP Relay >> Global Config.
The DHCP Server setting is used to specify DHCP server for the VLANs.
Both of the DHCP Server for the VLANs is at 192.168.0.1, so there should have two lists in the table.
Till now, all the configuration about the DHCP Relay is done. Let’s check if it does work.
Step 7:
Connect the PC to the ports belong to different VLANs, for example PC1 to port 1/0/4 and PC2 to 1/0/3. Then run the CMD, input the command: ipconfig/release and ipconfig/renew. The result shows like below in the different PCs.
The clients get IP from the DHCP server correctlly.
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
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
Deze website gebruikt cookies om de gebruikservaring te verbeteren, onlineactiviteiten te analyseren en om gebruikers de best mogelijke ervaring te bieden op onze website. U heeft de mogelijkheid op ieder moment de cookies te weigeren. Bekijk onze privacyverklaring voor meer informatie.
Deze website gebruikt cookies om de gebruikservaring te verbeteren, onlineactiviteiten te analyseren en om gebruikers de best mogelijke ervaring te bieden op onze website. U heeft de mogelijkheid op ieder moment de cookies te weigeren. Bekijk onze privacyverklaring voor meer informatie.
Standaard Cookies
Deze cookies zijn noodzakelijk voor de werking van de website en kunnen niet worden uitgeschakeld.
TP-Link
SESSION, JSESSIONID, 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
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
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Analyse en Marketing Cookies
Cookies voor analyse geven ons de mogelijkheid uw activiteiten op onze website te volgen en zo de functionaliteit van de website aan te passen en te verbeteren.
Marketing cookies kunnen op onze website worden geplaatst door externe adverteerders waar wij mee samenwerken om een profiel te creëren met uw interesses en u zo van relevante advertenties te kunnen voorzien op andere websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au