Asus XT8 - latency on local WiFi network between hosts

[mbordere]

I observe high latency between hosts on my local WiFi network.

Latencies from the hosts to the AP and the internet look fine, but latencies between hosts are very high.
Anyone experiencing something similar or has a suggestion to investigate this?

# ping the AP
user@host1:~$ ping 192.168.50.1
PING 192.168.50.1 (192.168.50.1) 56(84) bytes of data.
64 bytes from 192.168.50.1: icmp_seq=1 ttl=64 time=1.85 ms
64 bytes from 192.168.50.1: icmp_seq=2 ttl=64 time=3.51 ms
64 bytes from 192.168.50.1: icmp_seq=3 ttl=64 time=3.92 ms
64 bytes from 192.168.50.1: icmp_seq=4 ttl=64 time=4.01 ms
64 bytes from 192.168.50.1: icmp_seq=5 ttl=64 time=4.88 ms
64 bytes from 192.168.50.1: icmp_seq=6 ttl=64 time=3.89 ms
64 bytes from 192.168.50.1: icmp_seq=7 ttl=64 time=13.4 ms
64 bytes from 192.168.50.1: icmp_seq=8 ttl=64 time=3.48 ms
64 bytes from 192.168.50.1: icmp_seq=9 ttl=64 time=4.02 ms
64 bytes from 192.168.50.1: icmp_seq=10 ttl=64 time=3.78 ms
64 bytes from 192.168.50.1: icmp_seq=11 ttl=64 time=4.17 ms
64 bytes from 192.168.50.1: icmp_seq=12 ttl=64 time=3.48 ms
^C
--- 192.168.50.1 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11017ms
rtt min/avg/max/mdev = 1.846/4.534/13.444/2.769 ms

# ping something on the internet
user@host1:~$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=21.3 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=17.8 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=18.3 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=16.9 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=57 time=18.9 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=57 time=17.5 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=57 time=17.0 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=57 time=18.3 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=57 time=20.2 ms
^C
--- 1.1.1.1 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8011ms
rtt min/avg/max/mdev = 16.855/18.464/21.269/1.388 ms

# ping host2
user@host1:~$ ping 192.168.50.94
PING 192.168.50.94 (192.168.50.94) 56(84) bytes of data.
64 bytes from 192.168.50.94: icmp_seq=1 ttl=64 time=3.56 ms
64 bytes from 192.168.50.94: icmp_seq=2 ttl=64 time=64.8 ms
64 bytes from 192.168.50.94: icmp_seq=3 ttl=64 time=87.4 ms
64 bytes from 192.168.50.94: icmp_seq=4 ttl=64 time=149 ms
64 bytes from 192.168.50.94: icmp_seq=5 ttl=64 time=30.6 ms
64 bytes from 192.168.50.94: icmp_seq=6 ttl=64 time=52.3 ms
64 bytes from 192.168.50.94: icmp_seq=7 ttl=64 time=75.6 ms
64 bytes from 192.168.50.94: icmp_seq=8 ttl=64 time=97.4 ms
64 bytes from 192.168.50.94: icmp_seq=9 ttl=64 time=17.7 ms
^C
--- 192.168.50.94 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8013ms
rtt min/avg/max/mdev = 3.564/64.313/149.441/42.349 ms

# ping AP from host2
user@host2:~ $ ping 192.168.50.1
PING 192.168.50.1 (192.168.50.1) 56(84) bytes of data.
64 bytes from 192.168.50.1: icmp_seq=1 ttl=64 time=3.80 ms
64 bytes from 192.168.50.1: icmp_seq=2 ttl=64 time=3.97 ms
64 bytes from 192.168.50.1: icmp_seq=3 ttl=64 time=3.57 ms
64 bytes from 192.168.50.1: icmp_seq=4 ttl=64 time=3.67 ms
64 bytes from 192.168.50.1: icmp_seq=5 ttl=64 time=3.45 ms
64 bytes from 192.168.50.1: icmp_seq=6 ttl=64 time=3.71 ms
64 bytes from 192.168.50.1: icmp_seq=7 ttl=64 time=4.01 ms
64 bytes from 192.168.50.1: icmp_seq=8 ttl=64 time=4.61 ms
64 bytes from 192.168.50.1: icmp_seq=9 ttl=64 time=3.99 ms
^C
--- 192.168.50.1 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8013ms
rtt min/avg/max/mdev = 3.450/3.863/4.610/0.321 ms

# ping internet from host2
user@host2:~ $ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=22.0 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=18.7 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=19.2 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=18.0 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=57 time=18.3 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=57 time=19.7 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=57 time=15.4 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=57 time=16.7 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=57 time=16.8 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=57 time=14.1 ms
^C
--- 1.1.1.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9015ms
rtt min/avg/max/mdev = 14.117/17.897/22.013/2.146 ms

#ping host1
user@host2:~ $ ping 192.168.50.168
PING 192.168.50.168 (192.168.50.168) 56(84) bytes of data.
64 bytes from 192.168.50.168: icmp_seq=1 ttl=64 time=78.5 ms
64 bytes from 192.168.50.168: icmp_seq=2 ttl=64 time=99.4 ms
64 bytes from 192.168.50.168: icmp_seq=3 ttl=64 time=20.8 ms
64 bytes from 192.168.50.168: icmp_seq=4 ttl=64 time=42.4 ms
64 bytes from 192.168.50.168: icmp_seq=5 ttl=64 time=64.5 ms
64 bytes from 192.168.50.168: icmp_seq=6 ttl=64 time=247 ms
64 bytes from 192.168.50.168: icmp_seq=7 ttl=64 time=164 ms
64 bytes from 192.168.50.168: icmp_seq=8 ttl=64 time=31.7 ms
64 bytes from 192.168.50.168: icmp_seq=9 ttl=64 time=53.5 ms
64 bytes from 192.168.50.168: icmp_seq=10 ttl=64 time=75.9 ms
64 bytes from 192.168.50.168: icmp_seq=11 ttl=64 time=259 ms
64 bytes from 192.168.50.168: icmp_seq=12 ttl=64 time=20.2 ms
64 bytes from 192.168.50.168: icmp_seq=13 ttl=64 time=42.8 ms
^C
--- 192.168.50.168 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12016ms
rtt min/avg/max/mdev = 20.174/92.282/259.456/77.797 ms

 

[Smokey613]

My XT8 units in AP mode exhibit the same latency. So far it has not caused any issues.

 

[mbordere]

It doesn't really cause issues, but e.g. ssh feels laggy on the local network, while it should be very snappy. It's annoying, and should be easy enough to investigate for the firmware developers if it's easy to reproduce. Will try to contact their support team then.

 

[mbordere]

update:

It was not related to the XT8 but to

Wireless Power Saving (802.11 power save mode): Linux and many other operating systems have a power saving mode for WiFi that can cause delays in packet transmission, especially for traffic within the local network. This is part of the 802.11 WiFi standard and is designed to save battery power on portable devices. You can disable this feature on a Linux device using the following command:

sudo iwconfig wlan0 power off

Replace wlan0 with the name of your wireless interface if it's different.

Thanks to ChatGPT (and a helpful ASUS support guy that forced me to investigate a bit more )