Bug 2327527 - PEAP/MSCHAPv2 stopped working after update
Summary: PEAP/MSCHAPv2 stopped working after update
Keywords:
Status: CLOSED DUPLICATE of bug 2326839
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 41
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-19 23:44 UTC by tkeojqznx
Modified: 2025-01-03 08:30 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-01-03 08:30:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Network Manager Log (5.25 KB, text/plain)
2024-11-19 23:44 UTC, tkeojqznx
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.