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

Ask Fedora
, ,
1

Hello

After upgrading to Fedora 41, I’ve encountered an issue with connecting to my university’s WPA2-Enterprise network. This connection worked without issues on Fedora 40, but now the same configuration doesn’t seem to work.

Previously, I was able to connect by disabling MAC randomization by creating the conf file .
Editing the .nmconnection file by adding the line phase1-auth-flags=32.

With these settings, the connection was stable on Fedora 40, but on Fedora 41, I am no longer able to connect. I have tried reapplying the same configurations, but they don’t seem to work anymore.

Has anyone else experienced this after upgrading? If anyone has insights into changes in NetworkManager or WPA2-Enterprise handling in Fedora 41, or potential workarounds, I’d appreciate your help!

Thank you in advance for any guidance.

2 Likes
2

Hi there, I can confirm that I can still connect to my university’s WPA2-Enterprise (eduroam) after upgrading F40->F41 with unchanged settings. So “it is possible”, but there are many different variants, and even the version of the endpoint (radius server) can play a role. For example, I don’t override the MAC rand. for this connection, and it does not play a role because the endpoint does not care.

You can try journalctl -f in a terminal window while trying to connect. This can tell you which of the many phases does not work - basically it’s connecting to the WIFI access point, connecting to the radius server, authenticating with the latter, setting up the connection,

1 Like
3

My university uses fortinet not eduroam,also is is binded to the MAC Address.

the journalctl

Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6440] NetworkManager (version 1.50.0-1.fc41) is starting... (boot:4ece8eef-0baf-49a6-856b-b2cec0f37235)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6443] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf, 22-wifi-mac-addr.co>
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6475] manager[0x55fed48d5c90]: monitoring kernel firmware directory '/lib/firmware'.
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6502] hostname: hostname: using hostnamed
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6502] hostname: static hostname changed from (none) to "LAPTOP-LAPTOP"
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6504] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6511] manager[0x55fed48d5c90]: rfkill: Wi-Fi hardware radio set enabled
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6511] manager[0x55fed48d5c90]: rfkill: WWAN hardware radio set enabled
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6524] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.50.0-1.fc41/libnm-device-plugin-adsl.so)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6546] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.50.0-1.fc41/libnm-device-plugin-bluetooth>
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6555] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.50.0-1.fc41/libnm-device-plugin-team.so)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6564] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.50.0-1.fc41/libnm-device-plugin-wifi.so)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6566] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.50.0-1.fc41/libnm-device-plugin-wwan.so)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6568] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6568] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6569] manager: Networking is enabled by state file
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6569] settings: Loaded settings plugin: keyfile (internal)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6575] dhcp: init: Using DHCP client 'internal'
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6576] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6584] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6587] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'externa>
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6590] device (lo): Activation: starting connection 'lo' (b0cbdc23-fa54-4648-a6d8-e577a6bcf4d8)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6595] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6600] settings: (enp2s0): created default wired connection 'Wired connection 1'
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.6600] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8592] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8599] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8601] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8601] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8606] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8615] modem-manager: ModemManager available
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8622] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8623] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8626] device (lo): Activation: successful, device activated.
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8675] device (wlan0): driver supports Access Point (AP) mode
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8678] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8690] device (wlan0): interface index 3 renamed iface from 'wlan0' to 'wlp3s0'
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8734] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.2/0000:03:00.0/ieee80211/phy0/>
Oct 30 08:36:11 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257571.8741] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Oct 30 08:36:12 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257572.4494] device (wlp3s0): set-hw-addr: set MAC address to BA:53:71:A7:67:A0 (scanning)
Oct 30 08:36:12 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257572.5330] device (wlp3s0): supplicant interface state: internal-starting -> disconnected
Oct 30 08:36:12 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257572.5331] Wi-Fi P2P device controlled by interface wlp3s0 created
Oct 30 08:36:12 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257572.5333] manager: (p2p-dev-wlp3s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Oct 30 08:36:12 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257572.5334] device (p2p-dev-wlp3s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Oct 30 08:36:12 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257572.5339] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'f>
Oct 30 08:36:12 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257572.5343] device (p2p-dev-wlp3s0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Oct 30 08:36:18 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257578.2375] manager: startup complete
Oct 30 08:36:39 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257599.5504] agent-manager: agent[21cb26b34c966652,:1.94/org.kde.plasma.networkmanagement/1000]: agent registered
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.0375] device (wlp3s0): Activation: starting connection 'UNI-Connect' (c537e3eb-4e4e-4ae8-8c2e-a14bef52d736)
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.0376] audit: op="connection-add-activate" uuid="c537e3eb-4e4e-4ae8-8c2e-a14bef52d736" name="UNI-Connect" pid=2>
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.0380] device (wlp3s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.0382] manager: NetworkManager state is now CONNECTING
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.0844] device (wlp3s0): set-hw-addr: set-cloned MAC address to F6:16:5D:A7:96:6B (stable-ssid)
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1101] device (wlp3s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1105] device (wlp3s0): Activation: (wifi) access point 'UNI-Connect' has security, but secrets are required.
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1105] device (wlp3s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1118] device (wlp3s0): supplicant interface state: disconnected -> interface_disabled
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1118] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> interface_disabled
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1231] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1232] device (p2p-dev-wlp3s0): supplicant management interface state: interface_disabled -> inactive
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1296] device (wlp3s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1297] device (wlp3s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1299] device (wlp3s0): Activation: (wifi) connection 'UNI-Connect' has security, and secrets exist.  No new se>
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1300] Config: added 'ssid' value 'UNI-Connect'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1300] Config: added 'scan_ssid' value '1'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1300] Config: added 'bgscan' value 'simple:30:-65:300'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1300] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1300] Config: added 'auth_alg' value 'OPEN'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1300] Config: added 'password' value '<hidden>'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1300] Config: added 'eap' value 'PEAP'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1300] Config: added 'fragment_size' value '1266'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1301] Config: added 'phase2' value 'auth=MSCHAPV2'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1301] Config: added 'identity' value 'user@domain'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1301] Config: added 'proactive_key_caching' value '1'
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1365] device (wlp3s0): supplicant interface state: inactive -> scanning
Oct 30 08:38:21 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257701.1365] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> scanning
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.0907] device (wlp3s0): supplicant interface state: scanning -> authenticating
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.0908] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> authenticating
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.0924] device (wlp3s0): supplicant interface state: authenticating -> associating
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.0924] device (p2p-dev-wlp3s0): supplicant management interface state: authenticating -> associating
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.2717] device (wlp3s0): supplicant interface state: associating -> associated
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.2717] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> associated
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.3269] device (wlp3s0): supplicant interface state: associated -> disconnected
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.3269] device (p2p-dev-wlp3s0): supplicant management interface state: associated -> disconnected
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.4174] device (wlp3s0): supplicant interface state: disconnected -> scanning
Oct 30 08:38:24 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257704.4175] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> scanning
Oct 30 08:38:25 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257705.0192] device (wlp3s0): supplicant interface state: scanning -> authenticating
Oct 30 08:38:25 LAPTOP-LAPTOP NetworkManager[1166]: <info>  [1730257705.0193] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> authenticating
4

The wpa supplicant does not finish authorization. I assume you redacted user@domain in the journal, which is fine. Is the set MAC address really the one you used to connect with? There are different modes: some create a random but stable MAC address (per configured connection). You may need to force usage of the hardware MAC address, or register a new one with your uni if you can.

5

This is not my MAC

set-hw-addr: set MAC address to BA:53:71:A7:67:A0 (scanning)
6

In that case I would try

[wifi]
cloned-mac-address=<the one you registered with>

or

[wifi]
cloned-mac-address=permanent

in your config. You can also set this from the connection editor GUI.

7

Doesn’t work

8

Any updates on this

9

Well, in the log above, what happens after the last line (“authenticating”)? It has to either succeed or fail.

I also noticed that you’re not using a CA, but I assume that’s unchanged from your F40 config. Hard to tell without knowing more about your provider.

10

It doesn’t require a CA.
The uni uses fortinet for firewall and has fortinet routers.

11

Hey, i have the same issue.

On F40 i had to enable legacy provider in openSSL config, since my eduroam uses TLS-1.0, but it was working fine.

On F41, I’m not able to connect.

The journal logs:

lis 04 12:11:41 T14 NetworkManager[17115]: <info>  [1730718701.1490] device (wlp0s20f3): supplicant interface state: disconnected -> authenticating
lis 04 12:11:41 T14 NetworkManager[17115]: <info>  [1730718701.1491] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> authenticating
lis 04 12:11:41 T14 NetworkManager[17115]: <info>  [1730718701.1987] device (wlp0s20f3): supplicant interface state: authenticating -> associating
lis 04 12:11:41 T14 NetworkManager[17115]: <info>  [1730718701.1987] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
lis 04 12:11:41 T14 NetworkManager[17115]: <info>  [1730718701.2202] device (wlp0s20f3): supplicant interface state: associating -> associated
lis 04 12:11:41 T14 NetworkManager[17115]: <info>  [1730718701.2202] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated
lis 04 12:11:44 T14 NetworkManager[17115]: <info>  [1730718704.4152] device (wlp0s20f3): supplicant interface state: associated -> disconnected
lis 04 12:11:44 T14 NetworkManager[17115]: <info>  [1730718704.4154] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> disconnected
lis 04 12:11:44 T14 NetworkManager[17115]: <info>  [1730718704.5154] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
lis 04 12:11:44 T14 NetworkManager[17115]: <info>  [1730718704.5155] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
lis 04 12:11:56 T14 NetworkManager[17115]: <info>  [1730718716.0890] device (wlp0s20f3): supplicant interface state: scanning -> authenticating
lis 04 12:11:56 T14 NetworkManager[17115]: <info>  [1730718716.0891] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating
lis 04 12:11:56 T14 NetworkManager[17115]: <info>  [1730718716.1446] device (wlp0s20f3): supplicant interface state: authenticating -> associating
lis 04 12:11:56 T14 NetworkManager[17115]: <info>  [1730718716.1447] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
lis 04 12:11:56 T14 NetworkManager[17115]: <info>  [1730718716.1714] device (wlp0s20f3): supplicant interface state: associating -> associated
lis 04 12:11:56 T14 NetworkManager[17115]: <info>  [1730718716.1715] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated
lis 04 12:11:59 T14 NetworkManager[17115]: <info>  [1730718719.3903] device (wlp0s20f3): supplicant interface state: associated -> disconnected
lis 04 12:11:59 T14 NetworkManager[17115]: <info>  [1730718719.3904] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> disconnected
lis 04 12:11:59 T14 NetworkManager[17115]: <info>  [1730718719.4904] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
lis 04 12:11:59 T14 NetworkManager[17115]: <info>  [1730718719.4906] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
lis 04 12:12:06 T14 NetworkManager[17115]: <warn>  [1730718726.7117] device (wlp0s20f3): Activation: (wifi) association took too long
lis 04 12:12:06 T14 NetworkManager[17115]: <info>  [1730718726.7118] device (wlp0s20f3): state change: config -> need-auth (reason 'none', managed-type: 'full')
lis 04 12:12:06 T14 NetworkManager[17115]: <warn>  [1730718726.7125] device (wlp0s20f3): Activation: (wifi) asking for new secrets
lis 04 12:12:08 T14 NetworkManager[17115]: <warn>  [1730718728.8690] device (wlp0s20f3): no secrets: User canceled the secrets request.
lis 04 12:12:08 T14 NetworkManager[17115]: <info>  [1730718728.8693] device (wlp0s20f3): state change: need-auth -> failed (reason 'no-secrets', managed-type: 'full')
lis 04 12:12:08 T14 NetworkManager[17115]: <info>  [1730718728.8699] manager: NetworkManager state is now CONNECTED_LOCAL
lis 04 12:12:08 T14 NetworkManager[17115]: <warn>  [1730718728.8705] device (wlp0s20f3): Activation: failed for connection 'eduroam'
lis 04 12:12:08 T14 NetworkManager[17115]: <info>  [1730718728.8709] device (wlp0s20f3): state change: failed -> disconnected (reason 'none', managed-type: 'full')
lis 04 12:12:08 T14 NetworkManager[17115]: <info>  [1730718728.8981] device (wlp0s20f3): set-hw-addr: reset MAC address to 38:7A:0E:2F:1B:D8 (scanning)
lis 04 12:12:08 T14 NetworkManager[17115]: <info>  [1730718728.9008] device (wlp0s20f3): supplicant interface state: scanning -> disconnected
lis 04 12:12:08 T14 NetworkManager[17115]: <info>  [1730718728.9008] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> disconnected
lis 04 12:12:08 T14 audit[17115]: AVC avc:  denied  { unlink } for  pid=17115 comm="NetworkManager" name="timestamps" dev="nvme0n1p3" ino=546734 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0
lis 04 12:12:08 T14 NetworkManager[17115]: <info>  [1730718728.9040] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
lis 04 12:12:08 T14 NetworkManager[17115]: <info>  [1730718728.9040] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive

The part with asking for new secrets is when GNOME re-prompts me for login and password, since i click cancel, the message in the journal reflects that.

12

I have found out what was the issue. In Fedora 41 OpenSSL now distrusts SHA-1 signatures by default so to fix this just run
update-crypto-policies --set FEDORA40

1 Like
13

That means that our root issue is different since this does not fix my case.

14

were you able to find a solution? I have this issue as well and neither setting crypto-policies to LEGACY nor adding phase1-auth-flags=32 could solve the issue for me. I fresh install of fedora 41, coming from Pop_os 22.04 where it worked flawlessly

15

Unfortunately no. I don’t have enough knowledge in this field to troubleshoot and the error I’m getting is very lacking in terms of clues where to search for.

16

I hope we can both get some help, it’s kind of an important deal

18

I have found a solution that works for me, I hope it can help you as well. This is a simple script a friend of mine wrote, I believe the important line in the script is nmcli connection modify [your wifi] 802-1x.phase1-auth-flags 32, but the script is automated in giving you prompts and restarting your wifi services once finished and works very well. Keep in mind that the script is written specifically for the wifi “eduroam”, if you want to use it for a wifi with another SSID you need to edit the script (specifically at line 16) and swap out eduroam with your wifi ssid

19

update-crypto-policies --set FEDORA40
It no longer seems to work
Mine gets stuck at configuring interface

20

the script I shared before also seems to have stopped working

21

can confirm it does not work