@Vincent-TP Important information, Omada V6 ready access points, they need TCP port 29817 for wifi clients to appear in the Omada console. so if you have remote site then open up TCP 29817 TP-Link,...

@Vincent-TP Well, a bit of unnecessary trouble if port changes had been documented. But ok, for wifi clients to appear on controllers, TCP port 29817 must be opened in the firewall. Are there other...

@Vincent-TP EAP670v1 EU and EAP653v1 EU do not show wifi clients with Omada version 6. downgraded to the official version and the clients became visible in Omada V6 it is the same with EAP610-Outdoor...

@Johnny66 You cannot block Wireguard with Router ACL, but if you have an Omada switch SGxxx or larger, you can use Switch ACL to block Wireguard.

@GRL yeah the new controller is a bit messy, especially the switch profiles. it seems poorly thought out, i hope it's just a bug in the beta version and will be fixed in the final release.

@Vincent-TP A lot of good things in this version, but I don't like how the switch profile has become. The ability to create a switch profile with VLAN configuration, you should get that back.