Bug 2327527

Summary: PEAP/MSCHAPv2 stopped working after update
Product: [Fedora] Fedora Reporter: tkeojqznx
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 41CC: bgalvani, dcbw, ferferna, gnome-sig, ihuguet, lkundrak, mclasen, Rob.Tetour, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-01-03 08:30:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Network Manager Log none

Description tkeojqznx 2024-11-19 23:44:02 UTC 
I have been using Fedora to connect to my university's network fine until a few days ago, when an update permanently made PEAP/MSCHAPv2 stop working for both eduroam and the university network itself. A live USB of fedora KDE 41 works fine, and I have double checked the credentials. I am using an Intel AX201 WiFi Card in a Dell XPS 13 9310 Laptop. I have attached the networkmanager systemd logs. 

Reproducible: Always

Steps to Reproduce:
1. Connect to PEAP network
2. It does not work, even with CA certificate and correct credentials
Actual Results:  
It does not connect, hangs on "configuring interface" and fails on timeout

Expected Results:  
Connection is established
Comment 1 tkeojqznx 2024-11-19 23:44:54 UTC 
Created attachment 2058814 [details]
Network Manager Log
Comment 2 Íñigo Huguet 2024-11-20 16:17:17 UTC 
Got this feedback from wpa_supplicant maintainer: remove the pkcs11-provider package and stop/start wpa_supplicant. If connection is successful then this is a duplicate of BZ 2326839
Comment 3 Robin Tetour 2024-11-23 00:28:44 UTC 
(In reply to Íñigo Huguet from comment #2)
> Got this feedback from wpa_supplicant maintainer: remove the pkcs11-provider
> package and stop/start wpa_supplicant. If connection is successful then this
> is a duplicate of BZ 2326839

I also started to experience this bug after upgrade to Fedora 41 on Silverblue variant and I can confirm that override removing the pkcs11-provider package solved this issue completely on my end.
Comment 4 Íñigo Huguet 2025-01-03 08:30:35 UTC 
Thanks for the info. Closing as duplicate.

*** This bug has been marked as a duplicate of bug 2326839 ***