How to Manage Omada Devices at Different Sites Using Omada SDN Controller via VPN (Controller 5.0 or Above)

TL-SG2008P , TL-SG3452X , TL-SG2218P , TL-SG3452XP , EAP245( V3 V4 ) , ER7406 , EAP230-Wall , TL-SG2210P( V3 V3.20 V4 V5 ) , SG2210MP , TL-SX3008F , ER7206 , ER8411 , EAP115( V4 V4.20 V5 ) , TL-SL2428P( V4 V4.20 V5 V6 ) , TL-SX3016F , S4500-8G , SG2218 , SG3428 , Omada Software Controller( V5 ) , TL-SG3452P , TL-SG3428X , ER605 , EAP650-Outdoor , EAP772-Outdoor( V1 ) , SL2428P , S4500-8GHP2F , EAP653 UR , EAP660 HD , OC200 , AP9665 , S4500-16G2F , TL-SG3428XF , ER707-M2 , EAP673 , EAP110( V4 V5 ) , EAP670 , EAP235-Wall , TL-SG2210MP , SG3210 , SG3452 , SG3452X , TL-SG3210XHP-M2 , S5500-24GP4XF , EAP225( V3 V3.20 V4 V5 ) , TL-SG2428P , EAP610-Outdoor , EAP115-Wall , ER7212PC , SG3428XF , SG2428LP , EAP225-Wall( V2 ) , EAP225-Outdoor , EAP223 , SX3008F , SG3428MP , SG3428X , EAP725-Wall , SG3452P , EAP265 HD , SX3016F , SG2218P , EAP620 HD , SG2428P , SG2008P , SG3452XP , EAP613 , EAP610 , EAP653 , TL-SG3428 , TL-SG2218 , SG2210P , S5500-4XHPP2XF , EAP615-Wall , S5500-8MHP2XF , TL-SG3428MP , OC300 , TL-SG2008( V3 V4 ) , EAP650 , TL-SG3452 , TL-SG3210( V3 ) , EAP690E HD , TL-SX3206HPP , EAP623-Outdoor HD , SG3428XMP , EAP110-Outdoor( V3 V4 ) , TL-SG3428XMP , SX3206HPP
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.
As the network scenario shown below, Controller is running in the HQ, Router B in the Branch Office can communicate with Router A through VPN. In this article, we will introduce how to use the Controller in HQ to manage the devices in Branch Office via VPN.
Step1: Establish the IPsec VPN between Router A and Router B
Note: In this article, we suppose Router A is an Omada gateway managed by the Controller, in practice, it is enough if Router A can set up IPsec VPN.
1. Configuration on Router A
Go to Settings > VPN > VPN, and click on Create New VPN Policy button to create an IPsec rule for Branch Office:
Click on Advance Settings, set up the parameters as you like, then click on Create.
2. Configuration on Router B
1) Enter Router B’s Standalone interface, go to VPN > IPsec > IPsec Policy, and click Add to create an IPsec rule for HQ.
Click on Advanced Settings, set up the parameter corresponding to what you have set on Router A.
2) Go to VPN > IPsec > IPsec SA to check if the IPsec VPN tunnel is established successfully.
3) Go to System Tools > Controller Settings > Controller Inform URL, enter the Controller’s IP in the box.
Step2: Pre-configuration for Router B on the Controller
Create a new site for Branch Office in the Controller.
1) Pre-configuration of WAN
Go to Settings > Wired Network > Internet to configure the WAN override for Router B. The parameters should be the same as the Standalone mode.
2) Pre-configuration of LAN
Go to Settings > Wired Networks > LAN > Network to configure the LAN override for Router B. The parameters should be the same as the Standalone mode.
3) Pre-configuration of IPsec VPN
Go to Settings > VPN > VPN, and click on Create New VPN Policy button to create a new IPsec rule with the same parameters set in Router B Standalone mode.
Step3: Adopt Router B on the Controller
1) Since Controller’s IP has been told to Router B in step 1.2.3, Router B will appear in the Controller Devices list. Click adopt button to adopt it, the pre-configuration of WAN, LAN, VPN you just set will be sent to Router B automatically.
2) Go to Insight > VPN status > IPsec VPN to check the IPsec tunnel between Router A and Router B.
Step4:Manage Omada devices in different sites via different tools
Method 1: L3 Omada Discovery Utility
1) Download the Omada Discovery Utility and run it on PC2.
2) Select them and click the "Batch Setting" buttons in the lower right corner.
3) Specify the Center IP as Controller IP, and enter the devices’ Username and Password.
4) After settings succeed, the switch and AP will appear in the Controller Devices list.
Method 2: DHCP Option 138
1) Go to Settings > Wired Network > LAN > Networks to configure the DHCP of Router B.
2) Click on Advanced Settings to display the DHCP Options list, find Option 138 and enter the Controller IP.
3) Connect the Switch and EAP to Router B to obtain the IP via DHCP, the Controller’s IP will be sent to the switch and EAP via DHCP Option 138. After that, the devices will appear in the Controller Devices list with “PENDING” status.
Method 3: Web Management Page
1) Enter the switch’s IP on the browser to access its management page, go to SYSTEM > Controller Settings > Controller Inform URL and enter the Controller’s IP on the box.
2) Enter the EAP’s IP on the browser to access its management page, go to System > Controller Settings > Controller Inform URL and enter the Controller’s IP on the box.
3) Wait for a while, the devices will appear in the devices list with “PENDING” status.
Method 4: CLI
- For Switch
1) Enable the SSH on Switch’s Standalone management page.
2) Access the CLI of the Switch.
3) The commands for informing Switch of the Controller IP are as below.
enable
configure
controller inform-url 192.168.10.2
- For EAP
1) Enable SSH on EAP’s Standalone management page.
2) Access the CLI of the EAP.
3) The commands for informing EAP of the Controller IP are as below.
xsetctrladdr “192.168.10.2:29810”
Wait for a while, the Switch and EAP will appear in the Controller devices list with “PENDING” status.
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
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