EAP will not adopt to OC200 over VPN (IPsec)

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

EAP will not adopt to OC200 over VPN (IPsec)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
EAP will not adopt to OC200 over VPN (IPsec)
EAP will not adopt to OC200 over VPN (IPsec)
2023-03-28 14:51:52 - last edited 2023-03-28 14:53:12
Model: EAP225  
Hardware Version: V5
Firmware Version:

We have an OC200 with 11 EAP225 which work well in our main building, subnet 192.168.1.0/24.

 

We have a building across the road, which we linked via IPSec VPN (Draytek), subnet 192.168.2.0/24. We added another EAP in this second building.

Used DHCP option 138 to provide IP address of OC200 to the second EAP.

 

The EAP shows in OC200. When I Adopt, it starts adopting, then it goes to configuring, then it says configured. Then after about 45 seconds to 1 minute, it says Heartbeat Missed, and then it all starts again.


There is no firewalls in the way, I can ping both ways, but I cannot access the Web interface of the EAP from the main site. Is there some blocking of external IPs on the EAP which is blocking configuration by the OC200?

How can I fix this?


Thanks,

Carl

  0      
  0      
#1
Options
2 Reply
Re:EAP will not adopt to OC200 over VPN (IPsec)
2023-03-28 15:10:56
I found the option under 'Webserver' on the EAP for 'Layer 3 Connection', which I turned on, and then I can access the web UI from the other site. but still OC200 will not adopt. It adopts, then it configures, then it loses it and keeps going round in circles :(
  0  
  0  
#2
Options
Re:EAP will not adopt to OC200 over VPN (IPsec)
2023-03-28 19:06:36

To anybody else following:

 

I got this to work in the end.

 

I had to create a new Site in the Omada system, and put it in there. It would not work as part of the same Site at all.

  0  
  0  
#3
Options