You are not logged in.

#1 2022-01-20 10:34:51

f5VdL
Member
Registered: 2022-01-20
Posts: 2

Wi-fi timing out on ASK4 network

Hi all, first post here. Always was able to fix my Arch bugs by myself, but that one is mystical to me.

Somewhat recently moved to a student residence that relies on ASK4 (https://ask4internet.com/student-accommodation) for its network. While internet works fine wired and wireless for all of my other devices after I've created an ASK4 account and whatnot, my Arch laptop doesn't seem to fit in with the rest.
Every ten minutes or so starting from network login, all packets seem to start timing out. I don't get straight up disconnected, but my NetworkManager widget asks me to log in again (which doesn't work).
Firefox's captive network detection always says I need to log in, which redirects me to my network's login page which just throws a generic error - most likely because I'm already registered.

One of my first thoughts was a power saving related issue, but as far as I remember there's no power saving active (/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf has wifi.powersave = 2) ; I might have messed up disabling it though, somehow?
I think dmesg -w could potentially highlight problems, but nothing interesting shows up on it when the timeouts start.

I tried many things but the details of that are a bit hazy as this is a problem I tried fixing months ago but gave up on, apologies.
This may sound like a problem with my service provider, but I have no issues whatsoever on Ubuntu on a different laptop, or any other device ; this is definitely on Arch.

This is x86_64, kernel ver. Linux 5.15.5-arch1-1 (hadn't used my laptop in a while prior to writing this).

Any ideas would be much appreciated. Thanks in advance.

Offline

#2 2022-01-20 10:45:34

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 17,617

Re: Wi-fi timing out on ASK4 network

These portals often rely on a MAC to assign who's allowed to do what, try disabling MAC address randomization: https://wiki.archlinux.org/title/Networ … domization though this shouldn't  "randomly" happen after already having established a connection.

FWIW rather than looking at dmesg -W checking an actual journal with

sudo journalctl -b# Or -f if you want it to follow all events happening for the given time frame

might be more interesting as it's more likely one of the upper layers having an issue rather than something that would be logged by the kernel explicitly

Last edited by V1del (2022-01-20 10:47:20)

Offline

#3 2022-01-20 11:43:59

f5VdL
Member
Registered: 2022-01-20
Posts: 2

Re: Wi-fi timing out on ASK4 network

Didn't fix it, sadly, but thank you for your input. Having a look at the output of journalctl and I can try sharing whatever seems relevant... Not too familiar with its output, sadly. Some lines got cropped, I doubt whatever didn't appear on them is relevant.

Jan 20 11:23:26 xxxx-pc NetworkManager[354]: <info>  [1642677806.5173] dhcp4 (wlp58s0): state changed bound -> extended, address=XX.XX.XX.XX
Jan 20 11:23:26 xxxx-pc dbus-daemon[353]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':>
Jan 20 11:23:26 xxxx-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 20 11:23:26 xxxx-pc dbus-daemon[353]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 20 11:23:26 xxxx-pc systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 20 11:23:26 xxxx-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
Jan 20 11:23:26 xxxx-pc kernel: audit: type=1130 audit(1642677806.531:176): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/s>
Jan 20 11:23:34 xxxx-pc dbus-daemon[353]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.97' (uid>
Jan 20 11:23:34 xxxx-pc dbus-daemon[353]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jan 20 11:23:37 xxxx-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 20 11:23:37 xxxx-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? ad>
Jan 20 11:23:37 xxxx-pc kernel: audit: type=1131 audit(1642677817.031:177): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/s>
Jan 20 11:24:01 xxxx-pc audit[2916]: USER_ACCT pid=2916 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_time acct="username" exe="/usr/bin/cr>
Jan 20 11:24:01 xxxx-pc audit[2916]: CRED_ACQ pid=2916 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_unix,pam_env acct="username" exe="/usr/bin/crond" hostname=? >
Jan 20 11:24:01 xxxx-pc audit[2916]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=3 a1=7ffe99f732e0 a2=4 a3=3e8 items=0 ppid=351 pid=2916 auid=1000 uid=0 gid=0 euid=0 suid=0 fs>
Jan 20 11:24:01 xxxx-pc audit: PROCTITLE proctitle=2F7573722F62696E2F63726F6E64002D6E
Jan 20 11:24:01 xxxx-pc kernel: audit: type=1101 audit(1642677841.745:178): pid=2916 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_time ac>
Jan 20 11:24:01 xxxx-pc kernel: audit: type=1103 audit(1642677841.745:179): pid=2916 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_unix,pam_env acct="username" ex>
Jan 20 11:24:01 xxxx-pc kernel: audit: type=1006 audit(1642677841.745:180): pid=2916 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=12 res=1
Jan 20 11:24:01 xxxx-pc kernel: audit: type=1300 audit(1642677841.745:180): arch=c000003e syscall=1 success=yes exit=4 a0=3 a1=7ffe99f732e0 a2=4 a3=3e8 items=0 ppid=351 pid=2916 auid=10>
Jan 20 11:24:01 xxxx-pc kernel: audit: type=1327 audit(1642677841.745:180): proctitle=2F7573722F62696E2F63726F6E64002D6E
Jan 20 11:24:01 xxxx-pc audit[2916]: USER_START pid=2916 uid=0 auid=1000 ses=12 msg='op=PAM:session_open grantors=pam_loginuid,pam_limits,pam_unix acct="username" exe="/usr/bin/crond" ho>
Jan 20 11:24:01 xxxx-pc audit[2916]: CRED_REFR pid=2916 uid=0 auid=1000 ses=12 msg='op=PAM:setcred grantors=pam_unix,pam_env acct="username" exe="/usr/bin/crond" hostname=? addr=? termin>
Jan 20 11:24:01 xxxx-pc kernel: audit: type=1105 audit(1642677841.752:181): pid=2916 uid=0 auid=1000 ses=12 msg='op=PAM:session_open grantors=pam_loginuid,pam_limits,pam_unix acct="octa>
Jan 20 11:24:01 xxxx-pc kernel: audit: type=1110 audit(1642677841.752:182): pid=2916 uid=0 auid=1000 ses=12 msg='op=PAM:setcred grantors=pam_unix,pam_env acct="username" exe="/usr/bin/cr>
Jan 20 11:24:01 xxxx-pc audit[2916]: CRED_DISP pid=2916 uid=0 auid=1000 ses=12 msg='op=PAM:setcred grantors=pam_unix,pam_env acct="username" exe="/usr/bin/crond" hostname=? addr=? termin>
Jan 20 11:24:01 xxxx-pc audit[2916]: USER_END pid=2916 uid=0 auid=1000 ses=12 msg='op=PAM:session_close grantors=pam_loginuid,pam_limits,pam_unix acct="username" exe="/usr/bin/crond" hos>
Jan 20 11:24:01 xxxx-pc kernel: audit: type=1104 audit(1642677841.788:183): pid=2916 uid=0 auid=1000 ses=12 msg='op=PAM:setcred grantors=pam_unix,pam_env acct="username" exe="/usr/bin/cr>
Jan 20 11:24:01 xxxx-pc kernel: audit: type=1106 audit(1642677841.788:184): pid=2916 uid=0 auid=1000 ses=12 msg='op=PAM:session_close grantors=pam_loginuid,pam_limits,pam_unix acct="oct>
Jan 20 11:24:38 xxxx-pc systemd-timesyncd[344]: Timed out waiting for reply from XX.XX.XX.XX:123 (2.arch.pool.ntp.org).
Jan 20 11:24:48 xxxx-pc systemd-timesyncd[344]: Timed out waiting for reply from XX.XX.XX.XX:123 (2.arch.pool.ntp.org).
Jan 20 11:24:58 xxxx-pc systemd-timesyncd[344]: Timed out waiting for reply from XX.XX.XX.XX:123 (2.arch.pool.ntp.org).

This is what seems to happen around the timeouts.

Offline

#4 2022-01-22 11:18:12

tbg
Member
Registered: 2017-06-22
Posts: 72

Re: Wi-fi timing out on ASK4 network

A setting of "0" will totally disable power saving features in /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf, (not 2).

Offline

#5 2022-01-22 13:25:02

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 6,462

Re: Wi-fi timing out on ASK4 network

f5VdL wrote:

I can try sharing whatever seems relevant... Not too familiar with its output, sadly.

It's usually best to share the entire content, preferably from as brief a boot as possible, so that we (although probably not me) can spot anything you may have missed.

f5VdL wrote:

Some lines got cropped

Either pass the --no-pager option (--no-p for short) or pipe the output to a file to avoid cropping.

Offline

Board footer

Powered by FluxBB