Open aidansstuff opened 2 years ago
The same thing happens to me. I tried connecting to my school's wifi but it didn't work. I also tried using nmcli to see what was the problem. It reported that my device is unmanaged. It could be that the current wifi driver doesn't support wpa2 802.1x configuration
Are you using the preconfigured Asahi image with DE preinstalled? If so, Asahi is configured to use IWD. In fact if i use iwd as wifi backend, i also cannot connect to the eduroam Network.
You have to use wpa_supplicant. You can undo the NetworkManager iwd configuration pretty easy:
After the reboot you have to connect to all the Wireless Networks again, but this time it will work with 8021x
But there is a problem with (probably) the driver, because you cannot connect to a WPA3 Network with wpa_supplicant as backend.
@JustSomeNoiZ It worked. Thank you so much
wpa_supplicant does not support the WPA3 style this driver uses, that is why we use iwd instead.
Sounds like both are broken in different ways.
As for broken wpa3 with wpa_supplicant, has anything changed or been reported upstream?
There are patches posted in July but not yet merged as far as I can tell.
After the recent brcmfmac
driver rework, has anything changed with wpa3 & wpa_supplicant
?
The mentioned patches have been merged into wpa_supplicant
master branch:
https://w1.fi/cgit/hostap/commit/?id=236c0cfbcdf7459be1727afb7eb540c4ee081cbc
https://w1.fi/cgit/hostap/commit/?id=6cc78b3945d3271a66120378de101f7821fb0f2f
https://w1.fi/cgit/hostap/commit/?id=c3b8452e0e04038349fbfe757639ff3b377e98da
Now hope for a new release :)
Wifi (wpa2 enterprise) always asks me to set up the config every time and then won't connect. it just won't connect.