MattInWA wrote

Trying to set up the following:

 

ER605 Router: HW Version 2.0 Firmware 2.2.4 Build 20240119 Rel.44368

EAP610 HW Version 3.0 1.4.4 Build 20240312 Rel. 38091(5553)

Omada Software Controller version 5.13.30.8 on Debian 11, local only (no cloud setup for now).

 

I have all of the equipment running, but can not adopt the hardware into the software controller (it isn't visible and doesn't show up). On the controller page, under Devices, it shows "No Devices Found". How can I get these devices to show up? Both are on the latest firmware.

 

Topology is:

WAN>ER605>un-managed switch>EAP610 all in the same subnet 192.168.50.0/24

 

From the Debian box running the controller, the output of ss -tulpn | grep 2981 is:

 

udp   UNCONN 0      0                                           *:29810            *:*    users:(("jsvc",pid=10387,fd=475))
tcp   LISTEN 0      1024                                        *:29811            *:*    users:(("jsvc",pid=10387,fd=507))
tcp   LISTEN 0      1024                                        *:29812            *:*    users:(("jsvc",pid=10387,fd=491))
tcp   LISTEN 0      1024                                        *:29813            *:*    users:(("jsvc",pid=10387,fd=523))
tcp   LISTEN 0      1024                                        *:29814            *:*    users:(("jsvc",pid=10387,fd=539))
tcp   LISTEN 0      1024                                        *:29815            *:*    users:(("jsvc",pid=10387,fd=555))
tcp   LISTEN 0      1024                                        *:29816            *:*    users:(("jsvc",pid=10387,fd=571))

 

pertinent nftables firewall rules on the Debian box are:

 

 tcp dport 8088 counter accept comment "accept_Omada"
 tcp dport 8043 counter accept comment "accept_Omada"
 udp sport 29810 udp dport 29810 counter accept comment "accept_OmadaController"
 tcp sport 29811-29816 tcp dport 29811-29816 counter accept comment "accept_OmadaController"

 

Thanks for any input

 

 

Hi  @MattInWA 

If you have opened all the port the Controller and Omada Discovery Utility use, but the controller still failed to find & adopt the devices, here are some steps you may follow up to troubleshooting.

1. Try to get into the management page of ER605 and EAP, go to System/System tools > Controller Settings > Controller Inform URL, and input the IP address of software controller manually here.

2. Please download the Omada Discovery Utility and try to adopt the devices again.