Intranet lan traffic has too many ping spikes

Hi folks, i've been facing an issue let me explain. Currently i set up an edgerouter x as router, connected to a xiaomi dumb wifi access point with default firmware.
I also successfully configured the script for DSCP marking and it's working great.
But, intranet lan traffic has too many ping spikes. i've tried to ping my laptop from my phone, ping my phone from my router, ping my laptop from my router, all of these have completely unpredictable ping spikes, dancing from 3 to 100 ms. Has this something to do with my xiaomi dumb ap, or it could be something on the openwrt router that i need to change?
All of these pings were performed via wifi 5ghz which has no problems with internet latency, if i ping from my router to my ethernet pc, i get < 1 ms of latency, ideas? Thanks!

Edit: this is the ping between ethernet pc and wifi laptop, it seems like incremental, then it drops:

 ping 192.168.2.115
PING 192.168.2.115 (192.168.2.115): 56 data bytes
64 bytes from 192.168.2.115: icmp_seq=0 ttl=64 time=93.799 ms
64 bytes from 192.168.2.115: icmp_seq=1 ttl=64 time=15.257 ms
64 bytes from 192.168.2.115: icmp_seq=2 ttl=64 time=38.968 ms
64 bytes from 192.168.2.115: icmp_seq=3 ttl=64 time=63.309 ms
64 bytes from 192.168.2.115: icmp_seq=4 ttl=64 time=87.128 ms
64 bytes from 192.168.2.115: icmp_seq=5 ttl=64 time=111.109 ms
64 bytes from 192.168.2.115: icmp_seq=6 ttl=64 time=35.092 ms
64 bytes from 192.168.2.115: icmp_seq=7 ttl=64 time=56.751 ms
64 bytes from 192.168.2.115: icmp_seq=8 ttl=64 time=80.492 ms
64 bytes from 192.168.2.115: icmp_seq=9 ttl=64 time=104.341 ms
64 bytes from 192.168.2.115: icmp_seq=10 ttl=64 time=23.520 ms
64 bytes from 192.168.2.115: icmp_seq=11 ttl=64 time=49.726 ms
64 bytes from 192.168.2.115: icmp_seq=12 ttl=64 time=73.851 ms
64 bytes from 192.168.2.115: icmp_seq=13 ttl=64 time=97.581 ms
64 bytes from 192.168.2.115: icmp_seq=14 ttl=64 time=19.341 ms
64 bytes from 192.168.2.115: icmp_seq=15 ttl=64 time=42.970 ms
64 bytes from 192.168.2.115: icmp_seq=16 ttl=64 time=66.994 ms
64 bytes from 192.168.2.115: icmp_seq=17 ttl=64 time=91.084 ms
64 bytes from 192.168.2.115: icmp_seq=18 ttl=64 time=3.296 ms
64 bytes from 192.168.2.115: icmp_seq=19 ttl=64 time=36.826 ms
64 bytes from 192.168.2.115: icmp_seq=20 ttl=64 time=60.262 ms
64 bytes from 192.168.2.115: icmp_seq=21 ttl=64 time=84.351 ms
64 bytes from 192.168.2.115: icmp_seq=22 ttl=64 time=108.267 ms
64 bytes from 192.168.2.115: icmp_seq=23 ttl=64 time=29.769 ms
64 bytes from 192.168.2.115: icmp_seq=24 ttl=64 time=53.588 ms
64 bytes from 192.168.2.115: icmp_seq=25 ttl=64 time=77.519 ms
64 bytes from 192.168.2.115: icmp_seq=26 ttl=64 time=101.658 ms
64 bytes from 192.168.2.115: icmp_seq=27 ttl=64 time=24.636 ms
64 bytes from 192.168.2.115: icmp_seq=28 ttl=64 time=46.871 ms
64 bytes from 192.168.2.115: icmp_seq=29 ttl=64 time=1.050 ms
64 bytes from 192.168.2.115: icmp_seq=30 ttl=64 time=94.740 ms
64 bytes from 192.168.2.115: icmp_seq=31 ttl=64 time=16.584 ms
64 bytes from 192.168.2.115: icmp_seq=32 ttl=64 time=40.391 ms
64 bytes from 192.168.2.115: icmp_seq=33 ttl=64 time=66.911 ms
64 bytes from 192.168.2.115: icmp_seq=34 ttl=64 time=1.166 ms
64 bytes from 192.168.2.115: icmp_seq=35 ttl=64 time=112.374 ms
^C
--- 192.168.2.115 ping statistics ---
36 packets transmitted, 36 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.050/58.655/112.374/33.415 ms

I am seeing the same thing. Were you able to resolve this?

Pings to a mobile device on Wi-Fi often have very large delays due to power saving on the mobile device

1 Like

You are right, this desktop host had powersave on in NetworkManager. After changing it to value 2 (disabled) in /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf pings are down to about 2-6ms with the occasional, acceptable ~150ms spike (haven't optimized the wifi yet). This is opposed to being in the 60ms average with spikes into the 400ms range.

There sill could be cyclic scans of all frequencies to populate a list of APs in the surround... and these will also take a while?