You are not logged in.

#1 2025-02-24 14:28:07

mFixman
Member
Registered: 2011-09-12
Posts: 22

Auto-deauthenticating from eduroam about 95% of the time

I am trying to connect my Arch computer with NetworkManager to [eduroam](https://en.wikipedia.org/wiki/Eduroam), the international university WiFi internet access.

Connecting results in a lot of "deauthenticating from $MAC by local choice (Reason: 3=DEAUTH_LEAVING)" messages.

$ sudo dmesg -T
[...]
[Fri Feb 28 23:03:25 2025] wlan0: authenticate with dc:b8:08:db:3a:f1 (local address=e0:c2:64:d5:01:a1)
[Fri Feb 28 23:03:25 2025] wlan0: send auth to dc:b8:08:db:3a:f1 (try 1/3)
[Fri Feb 28 23:03:25 2025] wlan0: authenticated
[Fri Feb 28 23:03:25 2025] wlan0: associate with dc:b8:08:db:3a:f1 (try 1/3)
[Fri Feb 28 23:03:25 2025] wlan0: RX AssocResp from dc:b8:08:db:3a:f1 (capab=0x11 status=0 aid=1)
[Fri Feb 28 23:03:25 2025] wlan0: associated
[Fri Feb 28 23:03:25 2025] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by dc:b8:08:db:3a:f1
[Fri Feb 28 23:03:35 2025] wlan0: deauthenticating from dc:b8:08:db:3a:f1 by local choice (Reason: 3=DEAUTH_LEAVING)
[Fri Feb 28 23:03:37 2025] wlan0: authenticate with dc:b8:08:db:3a:e1 (local address=e0:c2:64:d5:01:a1)
[Fri Feb 28 23:03:37 2025] wlan0: send auth to dc:b8:08:db:3a:e1 (try 1/3)
[Fri Feb 28 23:03:37 2025] wlan0: authenticated
[Fri Feb 28 23:03:37 2025] wlan0: associate with dc:b8:08:db:3a:e1 (try 1/3)
[Fri Feb 28 23:03:37 2025] wlan0: RX AssocResp from dc:b8:08:db:3a:e1 (capab=0x411 status=0 aid=1)
[Fri Feb 28 23:03:37 2025] wlan0: associated
[Fri Feb 28 23:03:37 2025] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by dc:b8:08:db:3a:e1
[Fri Feb 28 23:03:47 2025] wlan0: deauthenticating from dc:b8:08:db:3a:e1 by local choice (Reason: 3=DEAUTH_LEAVING)
[Fri Feb 28 23:03:48 2025] wlan0: authenticate with dc:b8:08:db:3a:f1 (local address=e0:c2:64:d5:01:a1)
[...]

Disregard the incorrect timestamp. This seems to be a dmesg issue when suspending my computer, and can be fixed by rebooting; fixing the timestamp issue does not fix the disconnection issue.

My computer sometimes connects to eduroam after many tries, but I cannot figure out a reason of why this happens.

Existing posts mentioned that the problem might be from having several networking services running at the same time, but I think this is not the issue on my computer.

~ $ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
atd.service                              | multi-user.target.wants
avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
ntpd.service                             | multi-user.target.wants
nvidia-hibernate.service                 | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-suspend.service.wants
nvidia-suspend.service                   | systemd-suspend.service.wants
openvpn3-autoload.service                | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
thinkfan.service                         | multi-user.target.wants
thinkfan-sleep.service                   | sleep.target.wants
thinkfan-wakeup.service                  | sleep.target.wants
tlp.service                              | multi-user.target.wants
touchegg.service                         | multi-user.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

Does anybody know what the issue might be here, and how to fix it?

Last edited by mFixman (2025-02-24 14:28:48)

Offline

Board footer

Powered by FluxBB