@Fae I tried that firmware. It had the same issue. Once I moved the controller off the EAP the map updated showing the EAP connected to the switch as it should. My guess is there is some weird...

Bumping this as I feel this is something we need an answer to so we can determine if we are going to stick with the ER605 Gateway or replace it with a more capable IPv6 gateway.

Is there a way to accomplish this on the ER605 using the Omada Controller?

I know the ER605 is a NAT gateway for IPv4. This by default makes all the LAN devices behind the NAT unreachable from the Internet. If they do need access that is where port forwarding comes into...

Wondering if TP-LINK has plans to offer more powerful and feature rich gateway devices in the future? Something with more VPN throughput, support for things like wireguard, and more robust firewall...

Yeah I figured the IPv6 firewall rules were pretty light or nonexistent. Wondering if those are coming on the r605 or if there are plans for a more full featured gateway router/firewall in the future?