How to set up PPTP & L2TP VPN client with Omada Gateway in standalone mode
TL-ER7206 , TL-R605 , ER7206 , ER8411 , ER707-M2 , ER7406 , ER605
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.
Application scenario
Take the following topology as an example, we will configure (Router A) as PPTP&L2TP VPN Client to connect the PPTP&L2TP Server (Router B).
Configuration Steps
Step 1. Configure the 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
Step 2: Configure the PPTP&L2TP VPN client separately.
For L2TP VPN client, please go to “VPN>L2TP>L2TP client” and input the information from L2TP VPN server.
Note:
Account Name/Password: the user information created on VPN Server
Server IP: WAN IP of VPN Server
Pre-shared Key: the password created on VPN Server
Remote Subnet: the LAN Subnet of VPN Server which you can access via VPN connection
For PPTP VPN client, please go to “VPN>PPTP>PPTP client” and input the information from PPTP VPN server.
Note:
Account Name/Password: the user information created on VPN Server
Server IP: WAN IP of VPN Server
Remote Subnet: the LAN Subnet of VPN Server which you can access via VPN connection
For “Working Mode”, please check the explanation below:
NAT: NAT (Network Address Translation) mode allows the device to translate source IP address of L2TP packets to local IP address of L2TP tunnel.
Route: Route mode allows the device to forward L2TP packets via routing protocol.
Step 3: Connect the PPTP&L2TP VPN client to PPTP&L2TP VPN servers and verify the connection.
1. Please go to “VPN>PPTP&L2TP>Tunnel list” to check the connection for both PPTP&L2TP VPN server and client.
2. Try to ping the LAN IP from VPN server (Router B) on VPN client (Router A), it would get reply from VPN server.
The above two methods mean the VPN tunnel establishes successfully between the VPN client and VPN server.
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
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
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