Unable to connect to WPA2-Enterprise after upgrading to Fedora 41

Ask Fedora
, ,
22

Same problem, a reddit user pointed me in the right direction:

https://www.reddit.com/r/Fedora/comments/1gt6wi3/for_anyone_who_cannot_connect_to_wpa2_enterprise/

the culprit seems to be the update of the package pkcs11-provider to version 0.5-4.
after i removed it completely(was only a weak dependency on my system) I have been able to login to eduroam again.

i filed a bugreport:
https://bugzilla.redhat.com/show_bug.cgi?id=2326839

7 Likes
23

After running sudo dnf remove pkcs11-provider and then rebooting the wifi worked. Thanks !

2 Likes
24

Can confirm removing after removing pkcs11-provider the connection is back up.
Great

25

what is the purpose of this package, can it be removed safely?

26

Does not work in my case. The logs are exactly the same as the ones I provided earlier.

27

Has any of you tried uncommenting the “early” line in that config?

28

After uninstalling pkcs11-provider its working now

1 Like
29

My problem was specifically with eduroam, I tried everything in this thread. But that all didn’t seem to work. What eventually helped for me was this arch wiki page;

https://wiki.archlinux.org/title/Network_configuration/Wireless#eduroam

Which links to this “Configuration Assistant Tool”;

https://cat.eduroam.org/

Which after downloading it for your uni/school you can run the python file and fill in your credentials there. After that, my connection was working again.

I had the same kind of errors as @miosp (Jan Ludwina)

30

This helped. Thanks.

31

This worked, thank you.

For the context, same situation, upgraded from Fedora 40 to 41 and couldn’t connect to eduroam anymore. It was stuck in the loop of asking me for a password.

NetworkManager logs contained this output:

NetworkManager[1374]: <info>  [1732031960.9486] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
NetworkManager[1374]: <info>  [1732031960.9487] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
NetworkManager[1374]: <info>  [1732031962.4774] device (wlp0s20f3): supplicant interface state: scanning -> authenticating
NetworkManager[1374]: <info>  [1732031962.4775] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating
NetworkManager[1374]: <info>  [1732031962.5278] device (wlp0s20f3): supplicant interface state: authenticating -> associating
NetworkManager[1374]: <info>  [1732031962.5280] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
NetworkManager[1374]: <info>  [1732031962.5482] device (wlp0s20f3): supplicant interface state: associating -> associated
NetworkManager[1374]: <info>  [1732031962.5483] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated
NetworkManager[1374]: <warn>  [1732031986.4557] device (wlp0s20f3): Activation: (wifi) association took too long
NetworkManager[1374]: <info>  [1732031986.4558] device (wlp0s20f3): state change: config -> failed (reason 'no-secrets', managed-type: 'full')
NetworkManager[1374]: <warn>  [1732031986.4569] device (wlp0s20f3): Activation: failed for connection 'eduroam'
NetworkManager[1374]: <info>  [1732031986.4581] device (wlp0s20f3): state change: failed -> disconnected (reason 'none', managed-type: 'full')
32

Thank you! Removing the package fixed it for me! I can connect to my university wifi again. It used to work fine, I guess before the package was upgraded to the version you pointed out

33

I can confirm! Removing the package fixed it for me

Thank you

34

I asked on the devel list. This bug can probably be fixed in wpa_supplicant, but the suggested fix right now is to just uninstall pkcs11-provider. Most users don’t need to have it installed anyway.

35

Alternatively, you can uncomment the “early” line in the config and restart wpa_supplicant. Both worked for me.

1 Like
36

For me, uncommenting the lines as indicated in the reddit-post worked.

/etc/ssl/openssl.cnf

[provider_sect]
default = default_sect
legacy = legacy_sect               # <-- uncommnet this line
[default_sect]
activate = 1

[legacy_sect]                      # <-- uncommnet this line
activate = 1                       # <-- uncommnet this line```
37

Having the same issue on Silverblue 41. Would the fix be different from Workstation? I’ve gone back to a deployment of 40 for the time being. Considering waiting until this bug is fixed via an update in 41 before reverting to it.

38

For me, it worked by uninstalling pkcs11-provider and then reinstalling it.