Business Community > All Threads > Discovering WAPs on another network
< All Threads

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.
Discovering WAPs on another network
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?

  0      
 
  0      
 
#1
Options
1 Accepted Solution
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.

 

See also these FAQs:

 

https://www.tp-link.com/de/support/faq/2580/

https://www.tp-link.com/de/support/faq/2513/

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
Recommended Solution
  1  
  1  
#2
Options
2 Reply
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.

 

See also these FAQs:

 

https://www.tp-link.com/de/support/faq/2580/

https://www.tp-link.com/de/support/faq/2513/

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
Recommended Solution
  1  
  1  
#2
Options
Re:Discovering WAPs on another network
2020-02-21 17:37:30

@R1D2 

 

Thank you very much that sounds great.    I did manage to connect the WAPS by using the discovery tool and setting the server address.  They then connected and worked fine without any other additional rules on the firewall.

 

I'm thinking if I add the 138 option to the network the WAPS sit on then if I add new ones they should pick this up and make the connection themselves.

 

 

 

 

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 876

Replies: 2

Related Articles
Can my WAPs be in a mesh network?
343 0
Discovery Utility not discovering any devices
2396 0
Adopting devices from another network to my controller
160 0
My WAPS are causing my DHCP server to mark all available IPs as bad addresses
930 0
No 5G on one of my Omada WAPs
713 0
Cameras not auto discovering on TP-Link NVR
532 8
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.