Re: Bug report: Can connect with 'wext', but not 'nl80211'

On Wed, 2022-11-30 at 20:44 +0100, Matthias G. wrote:
> Hello,
>=20
> I hope this is the right place to report. I can connect via WiFi to my LT=
E router with the legacy 'wext' driver but not with 'nl80211'.
>=20
> The router is a rebranded version of this one:
> https://forum.openwrt.org/t/alcatel-tlc-hh40-lte-router-based-on-openwrt/=
77580
>=20
> This command fails:
> # wpa_supplicant -c wpa-home-lte.conf -i wlan0
>=20
> wlan0: SME: Trying to authenticate with dc:9b:d6:de:d4:27 (SSID=3D'<redac=
ted>' freq=3D2452 MHz)
> wlan0: Trying to associate with dc:9b:d6:de:d4:27 (SSID=3D'<redacted>' fr=
eq=3D2452 MHz)
> wlan0: SME: Trying to authenticate with dc:9b:d6:de:d4:27 (SSID=3D'<redac=
ted>' freq=3D2452 MHz)
> wlan0: Trying to associate with dc:9b:d6:de:d4:27 (SSID=3D'<redacted>' fr=
eq=3D2452 MHz)
> wlan0: SME: Trying to authenticate with dc:9b:d6:de:d4:27 (SSID=3D'<redac=
ted>' freq=3D2452 MHz)
> wlan0: Trying to associate with dc:9b:d6:de:d4:27 (SSID=3D'<redacted>' fr=
eq=3D2452 MHz)
> wlan0: SME: Trying to authenticate with dc:9b:d6:de:d4:27 (SSID=3D'<redac=
ted>' freq=3D2452 MHz)
> wlan0: Trying to associate with dc:9b:d6:de:d4:27 (SSID=3D'<redacted>' fr=
eq=3D2452 MHz)
> wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=3D0 ssid=3D"<redacted>" auth_fail=
ures=3D1 duration=3D10 reason=3DCONN_FAILED
>=20
> while this succeeds:
> # wpa_supplicant -Dwext -c wpa-home-lte.conf -i wlan0
>=20
> Successfully initialized wpa_supplicant
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> wlan0: Trying to associate with dc:9b:d6:de:d4:27 (SSID=3D'<redacted>' fr=
eq=3D2452 MHz)
> wlan0: Associated with dc:9b:d6:de:d4:27
> wlan0: WPA: Key negotiation completed with dc:9b:d6:de:d4:27 [PTK=3DCCMP =
GTK=3DCCMP]
> wlan0: CTRL-EVENT-CONNECTED - Connection to dc:9b:d6:de:d4:27 completed [=
id=3D0 id_str=3D]
>=20
> Kernel logs, failure:
> Nov 30 20:24:41 papaya kernel: wlan0: authenticate with dc:9b:d6:de:d4:27
> Nov 30 20:24:41 papaya kernel: wlan0: bad VHT capabilities, disabling VHT
> Nov 30 20:24:41 papaya kernel: wlan0: Invalid HE elem, Disable HE
> Nov 30 20:24:41 papaya kernel: wlan0: 80 MHz not supported, disabling VHT
> Nov 30 20:24:42 papaya kernel: wlan0: send auth to dc:9b:d6:de:d4:27 (try=
 1/3)
> Nov 30 20:24:42 papaya kernel: wlan0: authenticated
> Nov 30 20:24:42 papaya kernel: wlan0: associate with dc:9b:d6:de:d4:27 (t=
ry 1/3)
> Nov 30 20:24:42 papaya kernel: wlan0: associate with dc:9b:d6:de:d4:27 (t=
ry 2/3)
> Nov 30 20:24:42 papaya kernel: wlan0: associate with dc:9b:d6:de:d4:27 (t=
ry 3/3)
> Nov 30 20:24:42 papaya kernel: wlan0: association with dc:9b:d6:de:d4:27 =
timed out
> Nov 30 20:24:45 papaya kernel: wlan0: authenticate with dc:9b:d6:de:d4:27
> Nov 30 20:24:45 papaya kernel: wlan0: bad VHT capabilities, disabling VHT
> Nov 30 20:24:45 papaya kernel: wlan0: Invalid HE elem, Disable HE
> Nov 30 20:24:45 papaya kernel: wlan0: 80 MHz not supported, disabling VHT
> Nov 30 20:24:45 papaya kernel: wlan0: send auth to dc:9b:d6:de:d4:27 (try=
 1/3)
> Nov 30 20:24:45 papaya kernel: wlan0: authenticated
> Nov 30 20:24:45 papaya kernel: wlan0: associate with dc:9b:d6:de:d4:27 (t=
ry 1/3)
> Nov 30 20:24:45 papaya kernel: wlan0: associate with dc:9b:d6:de:d4:27 (t=
ry 2/3)
> Nov 30 20:24:46 papaya kernel: wlan0: associate with dc:9b:d6:de:d4:27 (t=
ry 3/3)
> Nov 30 20:24:46 papaya kernel: wlan0: association with dc:9b:d6:de:d4:27 =
timed out
>=20

Sounds like the AP is broken and doesn't like some elements wpa_s
includes when nl80211 has certain capabilities ...

Not sure what we can do about that - maybe there's a way to selectively
disable certain capabilities in wpa_s?

johannes