Adoption failing / problems
All,
Could have continued on an older thread of mine on the a.m. topic but as they have been "solved", I thought to better open a new one.
Situation:
* Two sites (site A, site B), mangaged by a SW controller on site A
* Site B is remote, i.e., not easily reachable (can't just go next door to access devices)
* Setup pretty identical - two internet providers, DSL, WAN connection on both sites established by a Draytek modem and an ER8411 router
* Several Omada switches and Omada access points operational on both sites
* Internet on both sites constantly up, no problems here
* Site A runs on 192.168.0.0/24 (DHCP active plus trusted DHCP), Site B on 192.168.100.0/24 (DHCP active plus- if I remember correctly - trusted DHCP)
Problem:
* Site A was running behind a third party router together with a SOPHOS FW
* Due to e.o.l. of the SOPHOS solution, setup of A was changed and aligned to setup of site B, i.e., replacing 3rd party router and SOPHOS FW with an OMADA setup (full ER8411 implementation on 27.12.2024)
* OMADA controller shows "Adoption" for all devices on site B since 27.12.2024
What I did before migration:
* Verified that ports on Windows device are open and FW rules are active (checked already existing inbound FW rules: TCP - 8043, 8088,8843, 29811-29816, 27217 and UDP - 27001, 29810).
* Checked that rules apply to all profiles: domain, private, public
* Windows machine runs on profile "private"
* Created NAT rules on Site A - TCP 8043, 8088, 8843, 29811-29816, 27217 and UDP 27001, 29810 - for the target IP of the controller
Status quo:
* Old configuration (setup with 3rd party router on Site A and full Omada setup on site B) worked well (some glitches here and there buit all-in-all no problems)
Since change of configuration on Site A to Omada, devices on site B show "Adoption" status
* Internet works, devices and services on Site B have internet access and are externally reachable
What I noticed:
* Reboot of controller on Site A result in "Adopting" status for all devices on Site B
* Powering down and up of the switches on Site B result in "Connected" status (Router ER8411 still "Adopting")
* Powering down and up of all devices on Site B result in "Adopting" for all devices
* Also tried gateway ACL rules (LAN-> WAN & WAN in) for the protocols/ports needed. No change in behaviour.
Seems that the ER8411 has a problem, or? Completely puzzled and clueless.
Any ideas before I reconfigure the ER8411?
Thanks!
@MR.S Thanks!
Tried around with the protocols in the NAT rules and changed from "TCP" or "UDP" to "All" as in your example. Did not help.
What however helped and solved the problem was a pure coincidental activity: unplugged the controller from the switch port used and stuck into the ER8411 directly.
"Onboarding" process started immediately and - after a while - ended successfully.
All site B devices are now shown as "connected", the VPN tunnel between the two sites works, too.
No idea on the "why", but the result is OK. 
.
Solved.
Br's Thomas
You only need 29810 UDP and 29811-29816 TCP to adopt from remote site, so it should work. ACL rules are not needed, they are created automatically when you port forward.
I have a similar setup with an ER8411 at the site where the controller is and some remote sites with different Omada routers but have never had the problem you have. so if the port forward is correct and you delete the ACL rules you have created then it should work.
this is what my port forward looks like.
I've changed some ports so don't let that confuse you :-)
@MR.S Thanks!
Tried around with the protocols in the NAT rules and changed from "TCP" or "UDP" to "All" as in your example. Did not help.
What however helped and solved the problem was a pure coincidental activity: unplugged the controller from the switch port used and stuck into the ER8411 directly.
"Onboarding" process started immediately and - after a while - ended successfully.
All site B devices are now shown as "connected", the VPN tunnel between the two sites works, too.
No idea on the "why", but the result is OK. .
Solved.
Br's Thomas