[SOLVED] NetworkManager stuck at "configuring interface"

othersamo_ · 2026-01-05 21:27:54

Hello,
I have tried to connect to my home wifi today. I have it set up via network manager and so far everything worked as expected. However, when I tried to connect today, I got "Configuring network interface" for like 2 some time and then and I got disconnected. On other wifi networks (even eduroam) everything works as expected. However, my other devices (e.g. phone) can connect to my home wifi normally. I have not made any changes to my network setup. Here is the log I am getting:

Jan 05 22:19:21 Samo-PCFW NetworkManager[956]: <info>  [1767647961.0941] device (wlp2s0): supplicant interface state: disconnected -> scanning
Jan 05 22:19:21 Samo-PCFW NetworkManager[956]: <info>  [1767647961.0941] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Jan 05 22:19:21 Samo-PCFW NetworkManager[956]: <info>  [1767647961.4903] device (wlp2s0): supplicant interface state: scanning -> authenticating
Jan 05 22:19:21 Samo-PCFW NetworkManager[956]: <info>  [1767647961.4903] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
Jan 05 22:19:26 Samo-PCFW NetworkManager[956]: <info>  [1767647966.6557] device (wlp2s0): supplicant interface state: authenticating -> disconnected
Jan 05 22:19:26 Samo-PCFW NetworkManager[956]: <info>  [1767647966.6558] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected
Jan 05 22:19:27 Samo-PCFW NetworkManager[956]: <info>  [1767647967.1655] device (wlp2s0): supplicant interface state: disconnected -> scanning
Jan 05 22:19:27 Samo-PCFW NetworkManager[956]: <info>  [1767647967.1655] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Jan 05 22:19:30 Samo-PCFW NetworkManager[956]: <info>  [1767647970.4006] device (wlp2s0): supplicant interface state: scanning -> authenticating
Jan 05 22:19:30 Samo-PCFW NetworkManager[956]: <info>  [1767647970.4007] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
Jan 05 22:19:35 Samo-PCFW NetworkManager[956]: <info>  [1767647975.5665] device (wlp2s0): supplicant interface state: authenticating -> disconnected
Jan 05 22:19:35 Samo-PCFW NetworkManager[956]: <info>  [1767647975.5666] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected
Jan 05 22:19:36 Samo-PCFW NetworkManager[956]: <info>  [1767647976.5774] device (wlp2s0): supplicant interface state: disconnected -> scanning
Jan 05 22:19:36 Samo-PCFW NetworkManager[956]: <info>  [1767647976.5775] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Jan 05 22:19:36 Samo-PCFW NetworkManager[956]: <info>  [1767647976.8453] device (wlp2s0): supplicant interface state: scanning -> authenticating
Jan 05 22:19:36 Samo-PCFW NetworkManager[956]: <info>  [1767647976.8453] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
Jan 05 22:19:40 Samo-PCFW NetworkManager[956]: <warn>  [1767647980.7552] device (wlp2s0): Activation: (wifi) association took too long, failing activation
Jan 05 22:19:40 Samo-PCFW NetworkManager[956]: <info>  [1767647980.7553] device (wlp2s0): state change: config -> failed (reason 'ssid-not-found', managed-type: 'full')
Jan 05 22:19:40 Samo-PCFW NetworkManager[956]: <info>  [1767647980.7555] manager: NetworkManager state is now CONNECTED_LOCAL

Does anone have an idea what can be causing this? Thank you.

Last edited by othersamo_ (2026-01-10 09:35:48)

Beemo · 2026-01-06 07:22:57

I had the same symptoms (with the same log) happen to me before. Eventually I discovered it was interference from USB3.
My USB3 Ethernet adaptor makes my 2.4GHz mouse stutter, and my USB-C framework storage card makes the laptop unable to discover / connect to 6GHz.

othersamo_ · 2026-01-06 08:53:00

I have tried disconnecting all devices from my laptop (framework 16) but it did not help

seth · 2026-01-06 11:20:27

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Filtering for NM won't help here, the issue is w/ the wpa supplicant or the kernel (and no: please don't post isolated filters for those either)

othersamo_ · 2026-01-06 15:50:01

Sure, heere is the log: http://bin.christitus.com/ewovikesis.yaml

seth · 2026-01-06 17:03:41

Jan 06 16:42:09 Samo-PCFW kernel: mt7921e 0000:02:00.0 wlp2s0: renamed from wlan0
…
Jan 06 16:42:22 Samo-PCFW wpa_supplicant[1069]: wlp2s0: SME: Trying to authenticate with 78:9a:18:fe:74:94 (SSID='JulkaAndEmil' freq=2432 MHz)
Jan 06 16:42:22 Samo-PCFW kernel: wlp2s0: authenticate with 78:9a:18:fe:74:94 (local address=fc:b0:de:17:ff:33)
Jan 06 16:42:22 Samo-PCFW kernel: wlp2s0: send auth to 78:9a:18:fe:74:94 (try 1/3)
Jan 06 16:42:22 Samo-PCFW NetworkManager[938]: <info>  [1767714142.4021] device (wlp2s0): supplicant interface state: scanning -> authenticating
Jan 06 16:42:22 Samo-PCFW NetworkManager[938]: <info>  [1767714142.4021] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
Jan 06 16:42:22 Samo-PCFW wpa_supplicant[1069]: wlp2s0: SME: Trying to authenticate with 78:9a:18:fe:74:94 (SSID='JulkaAndEmil' freq=2432 MHz)
Jan 06 16:42:22 Samo-PCFW kernel: wlp2s0: authenticate with 78:9a:18:fe:74:94 (local address=fc:b0:de:17:ff:33)
Jan 06 16:42:22 Samo-PCFW kernel: wlp2s0: send auth to 78:9a:18:fe:74:94 (try 1/3)
Jan 06 16:42:22 Samo-PCFW kernel: wlp2s0: 78:9a:18:fe:74:94 unexpected authentication state: alg 3 (expected 3) transact 1 (expected 2)

Can you limit the AP to WPA2 ?
Alternatively try to https://wiki.archlinux.org/title/Networ … Fi_backend

othersamo_ · 2026-01-06 21:34:13

I went with the iwd backend for the network manager. This solved the issue with connecting - e.g. when I connect to my home network, it connects normally. However, the auto-connect stopped working.
So I have KDE with KDEWallet. When I boot the computer, it automatically connects to the wifi after unlocking the wallet. However, now I have to manually connect to the network, it will not work otherwise.
It also throws an error: <error> [1767735464.5358] iwd-manager[0x847e4e79530]: IWD device named wlan0 is not a Wifi device

Last edited by othersamo_ (2026-01-06 21:39:49)

seth · 2026-01-06 21:49:50

NM is supposed to handle the passwords, please post an updated journal.

othersamo_ · 2026-01-10 09:33:03

After some testing of iwd, it seems to be far more broken than wpa_supplicant (eventually wifi stopped working altogether underneath it) with errors saying "No interface provided".
I ended up using wpa_supplicant and changing the router to WPA2

Arch Linux

#1 2026-01-05 21:27:54

[SOLVED] NetworkManager stuck at "configuring interface"

#2 2026-01-06 07:22:57

Re: [SOLVED] NetworkManager stuck at "configuring interface"

#3 2026-01-06 08:53:00

Re: [SOLVED] NetworkManager stuck at "configuring interface"

#4 2026-01-06 11:20:27

Re: [SOLVED] NetworkManager stuck at "configuring interface"

#5 2026-01-06 15:50:01

Re: [SOLVED] NetworkManager stuck at "configuring interface"

#6 2026-01-06 17:03:41

Re: [SOLVED] NetworkManager stuck at "configuring interface"

#7 2026-01-06 21:34:13

Re: [SOLVED] NetworkManager stuck at "configuring interface"

#8 2026-01-06 21:49:50

Re: [SOLVED] NetworkManager stuck at "configuring interface"

#9 2026-01-10 09:33:03

Re: [SOLVED] NetworkManager stuck at "configuring interface"

Board footer