You are not logged in.

#1 2022-03-31 14:59:13

joaonunatings
Member
Registered: 2021-10-14
Posts: 28

NetworkManager keeps changing state on eduroam

Hi, lately I've been getting weird disconnects and state changes from NetworkManager.

This happens randomly throughtout the day.
Running:

journalctl -b -u NetworkManager

I get the following:

Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.0650] device (p2p-dev-wlp1s0): supplicant management interface state: completed -> authenticating
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.0651] device (wlp1s0): ip:dhcp4: restarting
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.1058] dhcp4 (wlp1s0): canceled DHCP transaction
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.1059] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.1060] dhcp4 (wlp1s0): state changed no lease
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.1061] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.1073] device (wlp1s0): supplicant interface state: authenticating -> associating
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.1074] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.1079] device (wlp1s0): supplicant interface state: associating -> associated
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.1079] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> associated
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.2711] device (wlp1s0): supplicant interface state: associated -> completed
Mar 31 15:41:25 NetworkManager[386]: <info>  [1648737685.2725] device (p2p-dev-wlp1s0): supplicant management interface state: associated -> completed
Mar 31 15:41:27 NetworkManager[386]: <info>  [1648737687.1351] dhcp4 (wlp1s0): state changed new lease, address=194.210.194.209
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.3927] device (wlp1s0): supplicant interface state: completed -> disconnected
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.3928] device (p2p-dev-wlp1s0): supplicant management interface state: completed -> disconnected
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.4938] device (wlp1s0): supplicant interface state: disconnected -> scanning
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.4939] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.5652] device (wlp1s0): supplicant interface state: scanning -> authenticating
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.5652] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> authenticating
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.5691] device (wlp1s0): supplicant interface state: authenticating -> associating
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.5691] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.5863] device (wlp1s0): supplicant interface state: associating -> associated
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.5864] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> associated
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.5864] device (wlp1s0): ip:dhcp4: restarting
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.6238] dhcp4 (wlp1s0): canceled DHCP transaction
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.6239] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.6240] dhcp4 (wlp1s0): state changed no lease
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.6241] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.7706] device (wlp1s0): supplicant interface state: associated -> 4way_handshake
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.7707] device (p2p-dev-wlp1s0): supplicant management interface state: associated -> 4way_handshake
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.7821] device (wlp1s0): supplicant interface state: 4way_handshake -> completed
Mar 31 15:41:29 NetworkManager[386]: <info>  [1648737689.7828] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed
Mar 31 15:41:31 NetworkManager[386]: <info>  [1648737691.6546] dhcp4 (wlp1s0): state changed new lease, address=194.210.194.209
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.0834] device (wlp1s0): supplicant interface state: completed -> authenticating
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.0834] device (p2p-dev-wlp1s0): supplicant management interface state: completed -> authenticating
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.0834] device (wlp1s0): ip:dhcp4: restarting
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.1104] dhcp4 (wlp1s0): canceled DHCP transaction
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.1105] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.1105] dhcp4 (wlp1s0): state changed no lease
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.1106] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.1121] device (wlp1s0): supplicant interface state: authenticating -> associating
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.1121] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.1130] device (wlp1s0): supplicant interface state: associating -> associated
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.1130] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> associated
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.2869] device (wlp1s0): supplicant interface state: associated -> completed
Mar 31 15:41:49 NetworkManager[386]: <info>  [1648737709.2880] device (p2p-dev-wlp1s0): supplicant management interface state: associated -> completed
Mar 31 15:41:51 NetworkManager[386]: <info>  [1648737711.1282] dhcp4 (wlp1s0): state changed new lease, address=194.210.194.209

As you can see, it keeps looping between: authenticating -> associating -> associated -> completed -> disconnected -> scanning

Last edited by joaonunatings (2022-04-04 14:55:03)


Sway on ASUS ZenBook UX434DA-UM433DA: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx, 16GB RAM, Samsung MZVLB1T0HALR-1TB SSD, Keychron K12 with Banana Switches Keyboard

Offline

#2 2022-03-31 17:40:42

-thc
Member
Registered: 2017-03-15
Posts: 204

Re: NetworkManager keeps changing state on eduroam

Please post the output of

systemctl list-unit-files  --type=service | grep enabled

Offline

#3 2022-03-31 20:25:06

joaonunatings
Member
Registered: 2021-10-14
Posts: 28

Re: NetworkManager keeps changing state on eduroam

$ systemctl list-unit-files --type=service | grep enabled
bluetooth.service                               enabled         disabled
clightd.service                                 enabled         disabled
getty@.service                                  enabled         enabled
NetworkManager-dispatcher.service               enabled         disabled
NetworkManager-wait-online.service              enabled         disabled
NetworkManager.service                          enabled         disabled
systemd-boot-update.service                     disabled        enabled
systemd-fsck-root.service                       enabled-runtime disabled
systemd-homed.service                           disabled        enabled
systemd-network-generator.service               disabled        enabled
systemd-networkd.service                        disabled        enabled
systemd-pstore.service                          disabled        enabled
systemd-remount-fs.service                      enabled-runtime disabled
systemd-resolved.service                        disabled        enabled
systemd-timesyncd.service                       enabled         enabled

Sway on ASUS ZenBook UX434DA-UM433DA: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx, 16GB RAM, Samsung MZVLB1T0HALR-1TB SSD, Keychron K12 with Banana Switches Keyboard

Offline

#4 2022-03-31 21:05:03

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 16,502

Re: NetworkManager keeps changing state on eduroam

Don't run conflicting network services, disable systemd-networkd if you intend to use networkmanager or vice versa

Last edited by V1del (2022-03-31 21:05:42)

Online

#5 2022-04-04 13:31:04

joaonunatings
Member
Registered: 2021-10-14
Posts: 28

Re: NetworkManager keeps changing state on eduroam

I have disabled system-networkd and it fixed the issue, thank you.

Last edited by joaonunatings (2022-04-04 13:31:22)


Sway on ASUS ZenBook UX434DA-UM433DA: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx, 16GB RAM, Samsung MZVLB1T0HALR-1TB SSD, Keychron K12 with Banana Switches Keyboard

Offline

#6 2022-04-04 14:57:14

joaonunatings
Member
Registered: 2021-10-14
Posts: 28

Re: NetworkManager keeps changing state on eduroam

joaonunatings wrote:

I have disabled system-networkd and it fixed the issue, thank you.

Nevermind, the problem still occurs. Also, I had the service already disabled.


Sway on ASUS ZenBook UX434DA-UM433DA: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx, 16GB RAM, Samsung MZVLB1T0HALR-1TB SSD, Keychron K12 with Banana Switches Keyboard

Offline

Board footer

Powered by FluxBB