[resolved] wireless network delay

netjunegg · 2024-07-04 01:40:10

A Debian and Arch Linux operating systems are installed on the computer, which serves as an SSH server for remote access.
The connection is made using Wi-Fi, and the client computer is also on the same Wi-Fi network.
The differences between the two systems are quite apparent. On Debian, everything is normal and SSH is smooth with no delay or occasional freezing. However, after installing Arch Linux recently, I noticed a clear delay and occasional freezes of up to two seconds.
The Arch Linux kernel is LTS. Has anyone else experienced this issue?

Last edited by netjunegg (2024-07-05 19:04:09)

ewaller · 2024-07-04 01:48:46

Nope. Delay after you type a character? Delay after you press enter?
What are you using to control your WiFi? NetworkManager?
What WiFi chipset are you using?
as a hunch, what is the output of find /etc/systemd/system ?

netjunegg · 2024-07-04 08:35:47

ewaller wrote:

Nope. Delay after you type a character? Delay after you press enter?
What are you using to control your WiFi? NetworkManager?
What WiFi chipset are you using?
as a hunch, what is the output of find /etc/systemd/system ?

Delay after I type a character.

Yes. NetworkManager.

intel ax200 (on a notebook)

```
$ find /etc/systemd/system
/etc/systemd/system
/etc/systemd/system/dbus-org.freedesktop.timesync1.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/dbus-org.bluez.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/smb.service
/etc/systemd/system/multi-user.target.wants/sshd.service
/etc/systemd/system/multi-user.target.wants/nginx.service
/etc/systemd/system/multi-user.target.wants/touchegg.service
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/network-online.target.wants
/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service
/etc/systemd/system/sysinit.target.wants
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/systemd/system/display-manager.service
/etc/systemd/system/bluetooth.target.wants
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/sockets.target.wants
/etc/systemd/system/sockets.target.wants/systemd-userdbd.socket
```

ewaller · 2024-07-04 14:30:19

That all looks rational [I was looking for things fighting for control of the NIC]. AX-200 is well supported.

Any chance the Arch Linux is really busy? (Is a core pegged at 100%)
Are all other variables accounted for? IPv6 v IPv4?
Any chance of an address collision?

What is the output of iw wlan0 station dump ?? (If your wireless NIC is called something else, modify as appropriate)

Maybe also the output of ip addr and ip route

Be advised this is a really old BBS system that does not understand markup. You need BBCode Code tags instead of ``` ```. https://bbs.archlinux.org/help.php#bbcode
That link is also below each message post box on the forums.

Last edited by ewaller (2024-07-04 14:30:55)

seth · 2024-07-04 14:40:49

https://wiki.archlinux.org/title/Benchmarking#iperf
Check the general network speed between the two hosts and inspect the system journal for iwlwifi issues, notably firmware crashes.
If this is a 2.4GHz network, BT might get in the way and if multiple known APs are in range (can be the same physical box and SSID w/ 2.4GHz and 5GHz BSSIDs), NM might start to jump between them.

netjunegg · 2024-07-04 15:04:09

ewaller wrote:

That all looks rational [I was looking for things fighting for control of the NIC]. AX-200 is well supported.
Any chance the Arch Linux is really busy? (Is a core pegged at 100%)
Are all other variables accounted for? IPv6 v IPv4?
Any chance of an address collision?
What is the output of iw wlan0 station dump ?? (If your wireless NIC is called something else, modify as appropriate)
Maybe also the output of ip addr and ip route
Be advised this is a really old BBS system that does not understand markup. You need BBCode Code tags instead of ``` ```. https://bbs.archlinux.org/help.php#bbcode
That link is also below each message post box on the forums.

It is not busy (cpu usage is below 1%)

IPV4.

There is no address collision.

$ iw wlan0 station dump
Station 36:98:b5:10:c9:de (on wlan0)
        inactive time:  7 ms
        rx bytes:       119697
        rx packets:     976
        tx bytes:       943573
        tx packets:     707
        tx retries:     133
        tx failed:      0
        beacon loss:    5
        beacon rx:      3413
        rx drop misc:   20
        signal:         -43 [-43, -50] dBm
        signal avg:     -49 dBm
        beacon signal avg:      -49 dBm
        tx bitrate:     245.0 MBit/s 80MHz HE-MCS 3 HE-NSS 2 HE-GI 2 HE-DCM 0
        tx duration:    0 us
        rx bitrate:     1200.9 MBit/s 80MHz HE-MCS 11 HE-NSS 2 HE-GI 0 HE-DCM 0
        rx duration:    0 us
        authorized:     yes
        authenticated:  yes
        associated:     yes
        preamble:       long
        WMM/WME:        yes
        MFP:            yes
        TDLS peer:      no
        DTIM period:    1
        beacon interval:100
        short preamble: yes
        short slot time:yes
        connected time: 425 seconds
        associated at [boottime]:       127407.969s
        associated at:  1720104733504 ms
        current time:   1720105157537 ms

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 98:8f:e0:60:9d:2b brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 70:1a:b8:46:69:41 brd ff:ff:ff:ff:ff:ff
    altname wlp0s20f3
    inet 192.168.1.80/24 brd 192.168.1.255 scope global noprefixroute wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::cca0:7492:e8a7:321/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

$ ip route
default via 192.168.1.1 dev wlan0 proto static metric 600
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.80 metric 600

Bye the way, I just tried wired connection and it is ok with no delay.

netjunegg · 2024-07-04 15:10:47

seth wrote:

https://wiki.archlinux.org/title/Benchmarking#iperf
Check the general network speed between the two hosts and inspect the system journal for iwlwifi issues, notably firmware crashes.
If this is a 2.4GHz network, BT might get in the way and if multiple known APs are in range (can be the same physical box and SSID w/ 2.4GHz and 5GHz BSSIDs), NM might start to jump between them.

I have not tried the tool. I just find something error with iwlwifi in the output of dmesg:

[ 6.012665] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination ------------------------------------- this line is red
[ 6.112408] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 6.112459] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 6.112509] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 6.112561] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[ 6.113737] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 5
[ 6.188117] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, with index: 1
[ 6.253551] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination ------------------------------------- this line is red
[ 6.353246] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 6.353297] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 6.353349] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 6.353402] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[ 6.354703] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 5
[ 6.680460] Bluetooth: hci0: Waiting for firmware download to complete
[ 6.680790] Bluetooth: hci0: Firmware loaded in 1419943 usecs
[ 6.680861] Bluetooth: hci0: Waiting for device to boot
[ 6.692328] i915 0000:00:02.0: [drm] Selective fetch area calculation failed in pipe A
[ 6.695859] Bluetooth: hci0: Device booted in 14667 usecs
[ 6.695861] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 ------------------------------------- this line is red
[ 6.695990] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-4150.ddc
[ 6.698846] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 6.702017] Bluetooth: hci0: Firmware timestamp 2024.14 buildtype 1 build 81454
[ 6.771961] Bluetooth: MGMT ver 1.22
[ 6.778050] NET: Registered PF_ALG protocol family

Does this tell something? And how to fix it?

Last edited by netjunegg (2024-07-04 15:11:27)

seth · 2024-07-04 15:51:28

Not outof context and the "WRT: Invalid buffer destination" is kinda normal.
The duplication smells like the FW crashed at least once but this is also only 7s into the boot and likely before eg. any ssh activity?

Please post your complete system journal for the boot:

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

netjunegg · 2024-07-05 00:42:55

seth wrote:

Not outof context and the "WRT: Invalid buffer destination" is kinda normal.
The duplication smells like the FW crashed at least once but this is also only 7s into the boot and likely before eg. any ssh activity?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

The result: http://0x0.st/Xahv.txt

seth · 2024-07-05 07:03:12

There's no issue w/ the network logged at all, you're on 5GHz (so there's no BT interference) with a good signal.
I'll point out though that the journal is only 3 minutes, but it does cover a ssh login.
There's also no eg. some radio scanning going on after that login.

I just tried wired connection and it is ok with no delay.

Makes clear that it's the wifi, though.

Have you tried the non-LTS kernel?
Try to disable power saving:

iwlwifi.power_save=0 iwlwifi.uapsd_disable=1 iwlwifi.d0i3_disable=1 iwlmvm.power_scheme=1 pcie_aspm=off

https://wiki.archlinux.org/title/Kernel_parameters and

iw dev wlan0 set power_save off # at runtime

netjunegg · 2024-07-05 07:53:36

seth wrote:

There's no issue w/ the network logged at all, you're on 5GHz (so there's no BT interference) with a good signal.
I'll point out though that the journal is only 3 minutes, but it does cover a ssh login.
There's also no eg. some radio scanning going on after that login.
I just tried wired connection and it is ok with no delay.
Makes clear that it's the wifi, though.
Have you tried the non-LTS kernel?
Try to disable power saving:
iwlwifi.power_save=0 iwlwifi.uapsd_disable=1 iwlwifi.d0i3_disable=1 iwlmvm.power_scheme=1 pcie_aspm=off
https://wiki.archlinux.org/title/Kernel_parameters and
iw dev wlan0 set power_save off # at runtime

It seems be fixed by this command:

iw dev wlan0 set power_save off # at runtime

Thanks.

seth · 2024-07-05 14:34:30

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

netjunegg · 2024-07-05 19:05:38

seth wrote:

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Done.

Arch Linux

#1 2024-07-04 01:40:10

[resolved] wireless network delay

#2 2024-07-04 01:48:46

Re: [resolved] wireless network delay

#3 2024-07-04 08:35:47

Re: [resolved] wireless network delay

#4 2024-07-04 14:30:19

Re: [resolved] wireless network delay

#5 2024-07-04 14:40:49

Re: [resolved] wireless network delay

#6 2024-07-04 15:04:09

Re: [resolved] wireless network delay

#7 2024-07-04 15:10:47

Re: [resolved] wireless network delay

#8 2024-07-04 15:51:28

Re: [resolved] wireless network delay

#9 2024-07-05 00:42:55

Re: [resolved] wireless network delay

#10 2024-07-05 07:03:12

Re: [resolved] wireless network delay

#11 2024-07-05 07:53:36

Re: [resolved] wireless network delay

#12 2024-07-05 14:34:30

Re: [resolved] wireless network delay

#13 2024-07-05 19:05:38

Re: [resolved] wireless network delay

Board footer