...
Various models of Android 10 devices fail to connect to APs running 8.10.105.0 through 8.10.122.0 or running 16.12 and above.
This problem affects only AP-COS APs, not IOS APs. Affected clients run Android 10 - but Samsung clients are not affected. For AireOS deployments, all WPA2/WPA3 WLANs are affected (802.1X or PSK), but not open SSIDs. For IOS-XE deployments: * all WLANs are affected, if Device Analytics are enabled * with Device Analytics disabled, only WPA2/WPA3 WLANs are affected.
Downgrade to 8.8 or below or If using PSK: >Set FT to "Enabled" >Enable PSK and FT+PSK under WLAN configuration If using dot1x: >Set FT to "Enabled" >Enable dot1x and FT+dot1x under WLAN configuration After 17.6 in IOS-XE need to disable following in the wlan config to avoid DEO_IE to be sent: no device-analytics no device-analytics pc-analytics no scheduler asr no security ft adaptive
This compatibility issue was triggered by the introduction of support for Adaptive FT for Android in 8.10/16.12.1. (The "DEO_IE".) Some Android 10 clients have a bug wherein, if they encounter a "DEO_IE", they fail to attempt to associate. For AireOS 8.10 and IOS-XE 16.12 deployments: * the DEO_IE should be advertised only if Adaptive FT is configured on the SSID * however, due to an AP bug, the DEO_IE is advertised even when standard (rather than Adaptive) FT is configured, or when FT is disabled entirely. * with this fix CSCvu24770, the DEO_IE will not be sent if Adaptive FT is not configured - this will allow affected Android clients to associate For IOS-XE 17.x deployments: * the DEO_IO should be advertised only if EITHER Adaptive FT or Device Analytics is enabled * with this fix CSCvu24770, to allow affected Android devices to associate on a WLAN, disable Device Analytics AND disable Adaptive FT. In order for affected Android devices to connect to an Adaptive FT SSID, they will need to have their driver updated to a version that fixes the client side bug.