How to Configure TP-Link Omada Gateway as OpenVPN Client

ER7206 , ER8411 , ER7412-M2 , ER706W-4G , ER7406 , ER605 , ER706W
Pembaruan terkini mungkin telah memperluas akses ke fitur yang dibahas dalam Tanya Jawab Umum ini. Kunjungi halaman dukungan produk Anda, pilih versi perangkat keras yang tepat untuk perangkat Anda, dan periksa bagian Lembar Data atau firmware untuk mengetahui penyempurnaan terbaru yang ditambahkan ke produk Anda. Harap perhatikan bahwa ketersediaan produk bervariasi menurut wilayah, dan model tertentu mungkin tidak tersedia di wilayah Anda.
Note:
ER7206 with firmware 1.2.3 Build 20221104 or above, and ER605 V2 with firmware 2.1.1 Build 20230115 or above support certificate + account. ER605 V1 only supports certificate.
Application scenario
Take the following topology as an example, we will configure Router A as OpenVPN Client to connect the OpenVPN Server (Router B).
Case 1. How to configure Omada gateway as OpenVPN client on controller mode
Step 1. Export Open VPN configuration file including username and password on Router B.
Step 2. Import the file to Router A.
Go to Settings > VPN and click + Create New VPN Policy.
Name: tplink
Status: Enabled
Purpose: Client to Site VPN
VPN type: VPN Client-OpenVPN
Mode: Certificate+Account
Username: admin
Password: 12345678
Remote Server: 172.30.30.198
Local Network type: Network.
Click Import to upload the OpenVPN file that ends in .ovpn generated by the OpenVPN server.
Note: Local network is used to specify the subnet of the VPN client to access VPN.
Step 3. Verify the connectivity of the OpenVPN tunnel
Go to Insights-->VPN status-->PPTP/L2TP/OpenVPN Client
Note: If there’s a tunnel, VPN has been established successfully.
Case 2. How to configure Omada gateway as OpenVPN client on standalone mode
Step 1. Export OpenVPN configuration file on Router A, including username and password.
Step 2. Import the file to Router B.
Go to VPN-->OpenVPN--> to click Add to create a new VPN policy.
Client Name: tplink
Mode: CA+PWD
Username: admin
Password: 12345678
Service Port: 1194
Remote Server: 172.30.30.198
Local Network: 192.168.2.1
Click browse to upload the OpenVPN file that ends in .ovpn generated by the OpenVPN server, and click import.
Note: Local network is used to specify the subnet of the VPN client to access VPN.
Step 3. Verify the connectivity of the OpenVPN Tunnel
Go to VPN-->OpenVPN-->OpenVPN Tunnel
Note: If there’s a tunnel, VPN has been established successfully.
Related FAQs
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.
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
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or