Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
My Omada Software Controller (on a Raspberry Pi) upgraded to version 5.3.1.
The 2 devices I have that are on firmware 5.0.7 are not adopting anymore.
Their status is alternating between provisioning and adopting.
How can I fix this?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Here are some screenshots:
https://www.dropbox.com/scl/fi/qloofqkq8lnamjkryea6o/Omada.paper?dl=0&rlkey=50nlzqjyoh66fds62ba6eo4zn
- Copy Link
- Report Inappropriate Content
Do you run in a docker? you need to open TCP 29814 or if you have controller in another VLAN or port NATed in to controller from remote site
they have change two ports without it being documented very well.
TCP 29814 for adoption
Software controller TCP 8043 and TCP 443 OC200 / OC300 For firmware update
- Copy Link
- Report Inappropriate Content
@shberge yes, I use https://github.com/mbentley/docker-omada-controller
It exposes port 29814: https://github.com/mbentley/docker-omada-controller/blob/master/Dockerfile.v5.3.x
- Copy Link
- Report Inappropriate Content
Ok, try to telnet from windows command prompt from network where the device is, use this command
telnet ip to controller 29814 eg. telnet 192.168.1.2 29814
if there answer on this port all ok
- Copy Link
- Report Inappropriate Content
@shberge thank you for trying to help me. This is my result: the test succeeded: https://www.dropbox.com/s/35udiil8m42m7nc/rJZzIYOSXA.png?dl=0
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@shberge yes, the exact same 2 devices are still "provisioning" or "adopting" all the time.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Yes 192.168.0.101 is the IP adress of the physical device the Omada controller is on (=a Raspberry Pi).
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1088
Replies: 9
Voters 0
No one has voted for it yet.