Home

Forums

Stories

Knowledge Base

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

< Controllers

[OMADA Controllers] Impossible to adopt APs in different Sites

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

[OMADA Controllers] Impossible to adopt APs in different Sites

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

mrismontic

2024-02-11 15:44:54 - last edited 2024-02-19 09:33:56

Posts: 1

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2023-11-19

[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.

1 Accepted Solution

d0ugmac1

LV5

2024-02-11 17:16:13 - last edited 2024-02-19 09:33:56

Posts: 2105

Helpful: 767

Solutions: 190

Stories: 0

Registered: 2022-03-05

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

3 Reply

d0ugmac1

LV5

2024-02-11 17:16:13 - last edited 2024-02-19 09:33:56

Posts: 2105

Helpful: 767

Solutions: 190

Stories: 0

Registered: 2022-03-05

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... >>

[OMADA Controllers] Impossible to adopt APs in different Sites

[OMADA Controllers] Impossible to adopt APs in different Sites

Information

Voters 0

Tags