Hi, Upgraded from 5.1.0 to 5.2.0 via Omada. Bricked all our EAP245v3 hardware. Couple of points: In Omada controller, I see that the access points have 5.2.0 loaded. So the upgrad worked, but after th

On-going Pre-release Firmware Trial for Omada Controllers Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 19th Sep, 2025) Omada_SDN_Controller_v6.0.0.23_Windows (Windows 10/11/Server, 64

mDNS accross VLANs works for me, however, when I join the same subnetwork from my VPN (WireGuard), it doesn't. I can still access resources through their IP.

I use Surfshark as a VPN provider and their WireGuard config require DNS settings and an address space on the interface, neither of which can be added through the gui - I'm sure the underlying impleme

I have two EAP653s configured to serve a WPA2 Enterprise / AES SSID with dynamic VLAN assignment via RADIUS. I have also enabled 802.11r for the network (see below) I have no other Omada hardware in m

Issue #1: Built-in Omada Radius server uses EAP-MD5-Challenge by default. This method is compromised and deprecated, and declined by the client machine for that reason. Issue #2: Built-in Omada Radius