OC200 cannot adapt AP via VPN site-to-site
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
my goal is to adopt TP-Link AP from site B to its controller on site A
- I can ping everything
- I can see AP from OC200 controller
- but my problem is I can't adopt AP to Controller
- and I can't access AP via web browser
Both site only have Private IP from ISP so I use free tier AWS and CHR with elastic IP
yes so far this is my best solution for VPN without Public IP
When I ping google (without VPN) on each site I believe first 2 hop is Private IP
is it port forwarding problem?
Dear @puttskii,
puttskii wrote
my goal is to adopt TP-Link AP from site B to its controller on site A
May I verify the model number of your EAP? Is it EAP220 as it's showing in the picture you uploaded?
If it is EAP220 and there is no other new EAP in your network, you may downgrade the OC200 to manage the EAP220 accordingly.
The OC200 1.7.x is bundled with Omada Controller V4, which can only configure and manage the EAP devices with supported firmware.
https://www.tp-link.com/support/download/OC200/#Firmware
The EAP220 has been discontinued for years, and the recommended Controller version is Omada Controller v2.5.x
https://www.tp-link.com/support/download/eap220/#Firmware
But it may be hard to find Omada Controller v2, you may use OC200 1.2.4(Controller v3) to have a try.
@Fae I'm sorry I believe it's EAP110-Outdoor V3
in my AWS Mikrotik CHR I tried accept all inbound traffic
I see the AP, I can ping it, but can't access web config or adopt
here is the picture of failed adoption 
EAP110 Firmware : 5.0.0 Build 20200914 Rel. 52854
I believe first try by default use admin/admin and asked to input again pretty sure username and password
now it's in standalone mode
no stock OC200 in my country, somewhere in SEA
and been waiting "Omada Cloud-Based Controller" for so long
if it's working I'm planning to change all my Unifi in all 7 branch