Issues connecting to WPA2 university wifi from Fedora 43

Ask Fedora
,
1

Hello,

For context, I used to run Fedora 41 and also had the same issues of connecting to my University’s wifi. My university uses WPA/WPA2, PEAP, and MSCHAPv2. It would keep prompting me to enter username and password. This same issue (with fedora 41) was solved by removing the package pkcs11-provider. However I now use Fedora 43 and removing that package did not work.

Here are the journalctl log messages:

Oct 30 15:47:04 fedora NetworkManager[983]: <info>  [1761853624.9406] device (wlp61s0): supplicant interface state: disconnected -> scanning
Oct 30 15:47:04 fedora NetworkManager[983]: <info>  [1761853624.9407] device (p2p-dev-wlp61s0): supplicant management interface state: disconnected -> scanning
Oct 30 15:47:11 fedora NetworkManager[983]: <warn>  [1761853631.9112] device (wlp61s0): Activation: (wifi) association took too long
Oct 30 15:47:11 fedora NetworkManager[983]: <info>  [1761853631.9113] device (wlp61s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Oct 30 15:47:11 fedora NetworkManager[983]: <warn>  [1761853631.9123] device (wlp61s0): Activation: (wifi) asking for new secrets
Oct 30 15:47:28 fedora NetworkManager[983]: <info>  [1761853648.1649] device (wlp61s0): supplicant interface state: scanning -> inactive
Oct 30 15:47:28 fedora NetworkManager[983]: <info>  [1761853648.1650] device (p2p-dev-wlp61s0): supplicant management interface state: scanning -> inactive
Oct 30 15:47:30 fedora NetworkManager[983]: <info>  [1761853650.8592] device (wlp61s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Oct 30 15:47:30 fedora NetworkManager[983]: <info>  [1761853650.8597] device (wlp61s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Oct 30 15:47:30 fedora NetworkManager[983]: <info>  [1761853650.8603] device (wlp61s0): Activation: (wifi) connection 'CMU-SECURE' has security, and secrets exist.  No new secrets needed.

Not sure where to go from here. Would appreciate any help.

1 Like
2

Also, I am able to connect to my personal hotspot.

1 Like
3

I’m having the same issue. I can’t test it right now (and I’m fairly new to Fedora), but have you tried temporarily setting the system crypto policy to LEGACY?

This isn’t recommended as a permanent fix because it allows older, less secure TLS algorithms, but it could help narrow down the problem and be a temporary workaround if you really need to connect sometimes.

I think it is:

sudo update-crypto-policies --set LEGACY

Then reboot.

And revert for safety:

sudo update-crypto-policies --set DEFAULT

And don’t forget to reboot :slight_smile:

4

I managed to connect. In my case, the CA certificate that the University provided no longer worked on newer versions of Fedora for some reason. Since I instructed Fedora to use that certificate to try to connect, it kept failing.

What solved it was actually ticking “No CA certificate is required” and I was able to connect. Because Fedora already trusts the certificate in question.

1 Like