On Fri, 2019-10-11 at 17:10 +0200, Matteo Fortini via networkmanager- list wrote: Hi, what driver are you using? sounds like https://bugs.archlinux.org/task/63397 best, Thomas > I'm using wpa_supplicant 2.9.3 > > I cannot connect to any fast transition (FT) networks. I attach a > debug log. > > This includes for instance all the Ubiquity networks, but I tested it > also on OpenWrt+Roaming (802.11r) > > It seems that the FT-XXX key_mgmt configuration which is set by NM > triggers some bug. > > Configuration which doesn't work: > > network={ > ssid="myNetwork" > scan_ssid=1 > proto=RSN > key_mgmt=WPA-EAP WPA-EAP-SHA256 FT-EAP FT-EAP-SHA384 > pairwise=CCMP > auth_alg=OPEN > bgscan="simple:30:-65:300" > eap=PEAP > identity="myuser" > password="*******" > fragment_size=1266 > proactive_key_caching=1 > } > > > Configuration which works: > > network={ > ssid="myNetwork" > scan_ssid=1 > proto=RSN > key_mgmt=WPA-EAP > pairwise=CCMP > auth_alg=OPEN > bgscan="simple:30:-65:300" > eap=PEAP > identity="myuser" > password="*******" > fragment_size=1266 > proactive_key_caching=1 > } > > My network card is a BCM4350 802.11ac Wireless Network Adapter > running on Linux 5.3 > > * wpasupplicant=2:2.4-1+deb9u4 (oldstable) *works*, but because > NetworkManager uses "Config: added 'key_mgmt' value 'WPA-EAP'" > * wpasupplicant=2:2.7+git20190128+0c1e29f-6 (stable) *doesn't work*, > but because NetworkManager uses "Config: added 'key_mgmt' value 'WPA- > EAP > WPA-EAP-SHA256 FT-EAP FT-EAP-SHA384'" > > Now I'm on wpasupplicant=2:2.9.3 and it doesn't work, either, for the > same config reason > > Apparently nm uses the capabilities and triggers the bug.
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
