@s42p Hey, how do you know this? I cannot find any sources to this. Thanks

To follow up, I noticed the issue is not isolated to wireless. I have a tv which is wired that didn't work until after doing the trick to get DHCP working by adjusting the settings in the LAN...

@Fae I can recreate the issue, where the DHCP is failing. If I reboot both the EAP660 (HD(US) v1.0, FW 1.1.1) and the Gateway (ER7206, FW 1.2.1) through the Omada, it will not lease IP addresses to...

As explained, once I edit the settings on the LAN, it starts to work, if I don't they all will be stuck with 169.* addresses. I have around four different VLANs setup, all of them use the gateway's...

Also it definitely happened while using FW 1.2.1

@Fae I mean, that none of devices will get an IP via DHCP, regardless of whether I have configured an Fixed IP or not, until I change the range.