Hi all, just found an error in eventlog regarding WiFi roaming message: the first AP display name is wrong - it always equals the second one (which is correct) the channel number is OK when I click on

Hi all, I’m observing a reproducible issue with client detection in Omada SDN when a single device (in my case a NAS) is configured with multiple IP addresses across different VLANs. Setup: Omada SDN

This Article Applies to Omada_Network_Application_v6.2.10.x_Windows (Windows 10/11/Server, 64-bit Recommended) Omada_Network_Application_v6.2.10.x_linux_x64.tar.gz Omada_Network_Application_v6.2.10.x_

Yesterday i got problems with one of my EAP655-Wall. It started with all Clients disconnecting from WLAN. EAP was not reachable. Then this happend. 0.251 is the fallback IP. AP-DG got IP address 192.1

This Article Applies to Omada_Network_Application_v6.2.0.x_Windows (Windows 10/11/Server, 64-bit Recommended) Omada_Network_Application_v6.2.0.x_linux_x64.tar.gz Omada_Network_Application_v6.2.0.x_lin

This Article Applies to Omada_SDN_Controller_v6.0.0.24_Windows (Windows 10/11/Server, 64bit Recommended) Omada_SDN_Controller_v6.0.0.24_linux_x64.tar.gz Omada_SDN_Controller_v6.0.0.24_linux_x64.deb Ov