What to do if you want to access the Internet with the local gateway rather than the PPTP/L2TP VPN Server

ER7206 , 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. Please note that product availability varies by region, and certain models may not be available in your region.
With Client-to-LAN (Client-to-Site) VPN, the VPN client can access the remote network resources. Once the VPN connection is established, all your traffic from Windows devices will be forwarded to the VPN server by default.
What to do if you want to visit the Internet with the local gateway, and visit the remote network with the VPN tunnel? Please follow the steps below.
Please follow this FAQ to configure the Client-to-LAN PPTP VPN server on TP-Link routers: https://www.tp-link.com/en/support/faq/3026/
Please follow this FAQ to configure the Client-to-LAN L2TP VPN server on TP-Link routers: https://www.tp-link.com/en/support/faq/3025/
Step 1. Set up Class A or B network for the LAN IP and VPN IP Pool.
It is recommended to set up Class A or B network for the LAN IP and VPN IP Pool on the VPN router, which will save you from manually typing some commands to add some routing entries on the Windows devices.
Class A network include IP addresses: 10.0.0.0 to 10.255.255.255; while Class B network include: 172.16.0.0 to 172.31.255.255.
Note: If you use a Class B address, make sure the second segments of the router's LAN IP and of the VPN IP Pool are the same. For example, if the router's LAN IP is 172.30.30.1/24, then the VPN IP Pool should be 172.30.X.Y, where X is different from 30.
Take the above figure as an example, here we set up the LAN IP of the VPN router as 172.30.30.1/24, and the VPN IP Pool as 172.30.50.1 – 172.30.50.20 (for standalone mode) or 172.30.50.1/24 (for Omada SDN Controller). After the VPN client is connected, it obtains a VPN IP as 172.30.50.1.
Configuration screenshot of the Omada Gateway in standalone mode.
Configuration screenshot of the Omada SDN Controller.
Step 2. Configure the PPTP/L2TP VPN adapters.
Go to Control Panel –> Network and Internet –> Network and Sharing Center –> Change Adapter Settings, then you will find the PPTP/L2TP VPN adapters. Right-click the adapter –> Properties –> Networking, Double-click “Internet Protocol Version 4” –> Advanced, then you will find the Advanced TCP/IP settings for the VPN.
By default, “Use default gateway on remote network” is enabled, all network requests, whether to the Internet or the remote network, will be forwarded via the VPN tunnel, and handled by the VPN server.
To access the remote network with VPN and the Internet with the local gateway, please uncheck “Use default gateway on remote network” and “Disable class based route addition”.
Questa faq è utile?
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
Grazie
We appreciate your feedback.
Click here to contact TP-Link technical support.
Questo sito utilizza i cookies per migliorare l'esperienza di navigazione, analizzare le attività online e offrire agli utenti una migliore user experience. Puoi disattivare o rifiutare il loro utilizzo in qualunque momento. Per maggiori informazioni consulta la nostra privacy policy .
Questo sito utilizza i cookies per migliorare l'esperienza di navigazione, analizzare le attività online e offrire agli utenti una migliore user experience. Puoi disattivare o rifiutare il loro utilizzo in qualunque momento. Per maggiori informazioni consulta la nostra privacy policy .
Basic Cookies
Questi cookies sono necessari per il corretto funzionamento del sito e non possono essere disattivati nel tuo sistema.
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
Analytics e Marketing Cookies
I cookies analitici ci permettono di analizzare le tue attività sul nostro sito allo scopo di migliorarne le funzionalità.
I marketing cookies possono essere impostati sul nostro sito dai nostri partner pubblicitari allo scopo di creare un profilo di tuo interesse e proporti contenuti pubblicitari rilevanti su altri siti.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au