Business Community > Controllers > [OMADA Controllers] Impossible to adopt APs in different Sites
< Controllers

[OMADA Controllers] Impossible to adopt APs in different Sites

[OMADA Controllers] Impossible to adopt APs in different Sites

[OMADA Controllers] Impossible to adopt APs in different Sites
[OMADA Controllers] Impossible to adopt APs in different Sites
2024-02-11 15:44:54 - last edited 2024-02-19 09:33:56
Tags: #Controller Installation #Adoption
Model: Omada Cloud-Based Controller  
Hardware Version:
Firmware Version:

Hello everyone,

I have two sites with TP-LINK 'EAP 245' access points. One site has an OMADA OC200 controller that works very well. I want to control the APs at the other site with this controller.

I have tried the usual method described in several articles, including TP-LINK's documentation, but I haven't achieved any results. After extensive testing and research, I discovered that the site with the controller is behind a CG-NAT, making it impossible to forward the traffic from the access points to this OMADA controller.

I attempted to use VPN tunnels such as Cloudflare and Tailscale, but I am unsure exactly where to configure the VPN tunnel.

Here is my topology:

Topo

Thank you for your assistance.

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:[OMADA Controllers] Impossible to adopt APs in different Sites-Solution
2024-02-11 17:16:13 - last edited 2024-02-19 09:33:56

  @mrismontic 

 

A few approaches come to mind:

 

1. replace the OC200 with a TPlink Cloud Controller, manage both sites in the cloud

2. link the two sites via Client-Server VPN tunnel (I suggest L2TP/IPsec** in LAN extension mode) and manually point your remote AP via URL to the local OC200 IP

3. find a public-IP VPN solution for your CGNAT site supported by your router

 

**if your CGNAT issue happens to be Starlink, then you have to drop the IPsec encryption as Elon doesn't allow ESP traffic (or didn't 2 years ago)--so just L2TP then

<< Paying it forward, one juicy problem at a time... >>
Recommended Solution
  0  
  0  
#2
Options
3 Reply
Re:[OMADA Controllers] Impossible to adopt APs in different Sites-Solution
2024-02-11 17:16:13 - last edited 2024-02-19 09:33:56

  @mrismontic 

 

A few approaches come to mind:

 

1. replace the OC200 with a TPlink Cloud Controller, manage both sites in the cloud

2. link the two sites via Client-Server VPN tunnel (I suggest L2TP/IPsec** in LAN extension mode) and manually point your remote AP via URL to the local OC200 IP

3. find a public-IP VPN solution for your CGNAT site supported by your router

 

**if your CGNAT issue happens to be Starlink, then you have to drop the IPsec encryption as Elon doesn't allow ESP traffic (or didn't 2 years ago)--so just L2TP then

<< Paying it forward, one juicy problem at a time... >>
Recommended Solution
  0  
  0  
#2
Options
Re:[OMADA Controllers] Impossible to adopt APs in different Sites
2024-02-14 14:59:59

  @d0ugmac1 

 

found a solution to my problem, perhaps valuable/useful for you, too.

 

Pls. see my post just above yours named "Access Point Detection"

 

Thomas

  0  
  0  
#3
Options
Re:[OMADA Controllers] Impossible to adopt APs in different Sites
2024-02-14 21:44:20

  @mrismontic 

 

So a variation of #2 suggested above made possible because it has a public static IP or DDNS address so leveraging the internet instead of a tunnel.  Thanks for updating this thread with the conclusion.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#4
Options

Information

Helpful: 0

Views: 299

Replies: 3

Tags

Controller Installation Adoption
Related Articles
problem in adding a device
244 0
adopting existing Omada gateway in new controller OC200
1084 0
Management VLAN in Omada SDN Controller > fail
1060 0
Export settings from Switch/Gateway to Omada Software Controller
170 0
Switching Between OC200 & Omada Software Controller
112 0
How to adopt Omada Gateway at another location with no cable.
302 0
About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.