Dear @wifiexpert, Thank you for your valued reply! I'd add that the following feature (set a fixed IP address for Devices like EAP) is supported on Omada Controller v5.0 and above. wifiexpert wrote...

Dear @shivamg42, shivamg42 wrote @Fae Is this the solution for V5 controllers and above? This solution is applied to Controller v4.4.3 and later version, so yes, it's for v5.

Dear @luxor84, luxor84 wrote The IP of the NTP server is always on the destination but I no see any traffic as a source... Is it the reason why there is in the log "Time renew failed, connecting NTP...

Dear @WirelessForEver, WirelessForEver wrote As an update to my situation, I switched to the Linux Omada Controller on Ubuntu and the adoption loop problem went away. On 5.0.29 on Server 2022 the...

This Article Applies to: Omada Controller v5.0.29 (Windows) Omada Controller v5.0.29 (Linux) OC200 1.14.2 with Built-in Controller v5.0.29 OC300 1.7.0 with Built-in Controller v5.0.29 Issue...

Dear @Alex_UTS, Alex_UTS wrote Model: OC300 Hardware Version: V1 Firmware Version: 1.7.0 Build 20211215 Rel.61008 @Fae Just made the update for OC300 to 5.0.29 from the Omada Cloud. All 68 AP EAP225...