How to configure Policy Routing on Dual WAN Router using the new GUI
TL-R600VPN( V4 ) , TL-ER6120( V2 V3 ) , TL-ER6020( V2 ) , TL-ER5120( V3 V4 ) , TL-R480T+( V9 ) , TL-R470T+( V6 )
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.
Policy Routing provides the network administrator with an accurate way to control the routing based on the policy. You could define different routing policies based on protocol, source/destination IP and source/destination port, and you could set effective time to make policy routing take effect in the specific time period.
There is an example of daily use below showing how to configure port-based policy routing on dual WAN router correctly:
A customer has a TL-ER6120 and he connects 3 computers to the LAN side of TL-ER6120 with IP address 192.168.0.2-192.168.0.4, all computers are routed to Internet by dual WAN ports, he plans to set policy routing rules for 2 computers which use 192.168.0.2 and 192.168.0.3, make WAN1 for web surfing, WAN2 for other Internet activities, in additional, he wants these routing rules only work in 8:00-18:00 on workday. In this case, how to configure policy routing in order to meet the need of this customer?
Step 1 Set up the IP Group.
Choose the menu Preferences->IP Group->IP Address, set up the IP Address for the client which you want to apply the Policy Routing.
Bind the IP address to IP group.
Step 2 Set up the Time Range for the Policy Routing effective time.
Choose the menu Preferences->Time Range, you can define the time-range entry on this page.
Step 3 Enable Load Balancing
Choose the menu Transmission -> Load Balancing->Basic Settings. Check Enable Load Balancing.
Note: Enable Load Balancing must be enabled if you want to configure Policy routing. Otherwise Policy routing won’t work normally.
Step 4 Set up the Policy Routing rules.
Choose the menu Transmission->Routing->Policy Routing.
The router will check the rules in the list by turns from top to bottom. We can set up two rules to meet the need of the customer. The first rule is for 192.168.0.2&192.168.0.3 to route the data whose destination port is 80(Web application use) to WAN1 only. The second rule is for route all ports of 192.168.0.2&192.168.0.3 to WAN2.
The first rule is as follows.
The second rule is as follows.
Note: The mode is usually “Priority” instead of “Only”. In priority mode, before routing traffics to specific WAN, the router would check its status based on Online Detection. If the WAN were offline, data would go through the other WAN with Internet access. While under Only mode, the rule always take effects, no matter the selected WAN is online or offline. Mostly the parameter should be “Priority”.
So the customer could make sure on the computers with IP address 192.168.0.2&192.168.0.3 data is transmitted via WAN1 when his computers visit HTTP web, and via WAN2 when they download or enjoy some other Internet activities. There is no policy routing set for 192.168.0.4, so the Internet activities on that computer are routed to both WANs randomly.
Note:
1.Policy Routing can help select the appropriate WAN port for data transmission, but when the router detects the WAN1 failed, the HTTP data also will be transmitted via WAN2.
2.Router provides some common service types. If the service you need is not in the service list, you can configure the Service Type by yourself. For example, if you want to configure service of TCP 8080, you can set up as follows.
Choose the menu Preferences->Service Type. Set up the Service Type according to protocol and source/destination port.
Looking for More
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.
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
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or