Discovering WAPs on another network

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

Discovering WAPs on another network

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

tre4b

2020-02-21 13:47:41 - last edited 2020-02-24 08:35:03

Posts: 2

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2020-02-21

Discovering WAPs on another network

2020-02-21 13:47:41 - last edited 2020-02-24 08:35:03

Model: EAP225

Hardware Version:

Firmware Version:

Hi there,

I have two EAP225 WAPS that are on a different physical networks to my Omada controller via ports on a firewall router. I can create rules etc. however at this point I have not been able to figure out what trafic needs to go between these networks to allow the EAP225s to be discovered and adopted.

I have read that Ports 29810-29813 are required for the devices to talk, however these do not seem to allow them to be discovered. Does anyone know what the pre-requisites are for getting this communication working?

1 Accepted Solution

R1D2

LV6

2020-02-21 14:07:58 - last edited 2020-02-24 08:35:03

Posts: 4334

Helpful: 1039

Solutions: 173

Stories: 3

Registered: 2015-12-05

Re:Discovering WAPs on another network-Solution

2020-02-21 14:07:58 - last edited 2020-02-24 08:35:03

For EAP discovery you need to open TCP ports 29811, 29812, 29813 and UDP port 29810 in the firewall on the Controller side. If you want to use portal functions or if you need remote web UI access to the Omada EAP Controller, TCP ports 8088 and 8043 must be opened, too.

As for setting the IP of the Controller in EAPs, use either the EAP Discovery Utility or DHCP option 138 (CAPWAP) in the network(s) where the EAPs reside.

Discovering WAPs on another network

Discovering WAPs on another network

Information

Voters 0

Tags