How to configure Omada Gateway as a PPTP/L2TP VPN Client to enable the VPN Server as Proxy Gateway for backend clients

G36W-4G , TL-ER7206 , ER605W , TL-R605 , ER7206 , ER8411 , ER707-M2 , ER706W-4G , ER7406 , ER605 , ER706W
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.
Application Scenario:
Take the following network topology as an example, we will configure Router B as PPTP/L2TP VPN Client to connect the PPTP/L2TP VPN Server (Router A).
Configuration Overview:
- Configure Router A as PPTP/L2TP VPN Server.
- Configure Router B as PPTP/L2TP VPN Client.
Case 1: All backend clients want to access the Internet via VPN Server.
Case 2: Specific backend clients want to access the Internet via VPN Server, which needs configuring Policy Routing on Router B (PPTP/L2TP VPN Client) for specific devices
Configuration Steps:
- Configure Router A as PPTP/L2TP VPN Server.
For detail configuration, please refer to the following articles:
How to establish an L2TP Server by Omada Gateway in Standalone mode
How to establish a PPTP Server by Omada Gateway in Standalone mode
- Configure Router B as PPTP/L2TP VPN Client.
Case 1: If you want all the backend clients to access the Internet via VPN Server,
please refer to the following article:
How to set up PPTP & L2TP VPN client with Omada Gateway in standalone mode
Note: Remote Subnet set to 0.0.0.0/0 would make all the backend clients to access the Internet via VPN Server by default.
Case 2: If you want specific backend clients to access the Internet via VPN Server,
please refer to the following article to begin with:
How to set up PPTP & L2TP VPN client with Omada Gateway in standalone mode
After last configuration, please refer to the following steps below:
- Configure Policy Routing on Router B (PPTP/L2TP VPN Client) for specific devices. (Here we take L2TP VPN Server and L2TP VPN Client as an example, and the configuration is the same for PPTP VPN Server and PPTP VPN Client.)
- Go to “Preferences>IP Group” to setup corresponding IP group and IP address range for specific devices which want to access the Internet via PPTP/L2TP VPN Server as a Proxy Gateway.
- Then go to “Transmission>Routing>Policy Routing” to create a rule for the devices of last step.
Here we select “Source IP” to “test1” which is the IP group name you configured of last step, and select “WAN“ to “L2TP” which means routing the relevant traffic of the clients in the IP Group into the L2TP VPN tunnel.
Note: Here we select “Destination IP” to “IPGROUP_ANY”, which means this routing rule would forward all the traffic of the clients in the selected IP Group.
- Verification.
(1) Without Policy Routing by default, the devices would access the Internet via their default gateway 192.168.10.1 by verifying with command “tracert 8.8.8.8”.
(2) With Policy Routing, the devices would access the Internet by using the VPN Server 192.168.0.1 as a Proxy Gateway by verifying with the command “tracert 8.8.8.8” as well.
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
Your Privacy Choices
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
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_banner, tp_privacy_base, tp_privacy_marketing, 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
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