4ms Ping to Openwrt AP

That's normal when power saving is enabled. I have one device too:
PING 192.168.1.133 (192.168.1.133) 56(84) bytes of data.
64 bytes from 192.168.1.133: icmp_seq=1 ttl=64 time=274 ms
64 bytes from 192.168.1.133: icmp_seq=2 ttl=64 time=18.8 ms
64 bytes from 192.168.1.133: icmp_seq=3 ttl=64 time=40.9 ms
64 bytes from 192.168.1.133: icmp_seq=4 ttl=64 time=63.8 ms
64 bytes from 192.168.1.133: icmp_seq=5 ttl=64 time=86.4 ms
64 bytes from 192.168.1.133: icmp_seq=6 ttl=64 time=181 ms
64 bytes from 192.168.1.133: icmp_seq=7 ttl=64 time=203 ms
64 bytes from 192.168.1.133: icmp_seq=8 ttl=64 time=226 ms
64 bytes from 192.168.1.133: icmp_seq=9 ttl=64 time=249 ms
64 bytes from 192.168.1.133: icmp_seq=10 ttl=64 time=272 ms
64 bytes from 192.168.1.133: icmp_seq=11 ttl=64 time=17.7 ms
64 bytes from 192.168.1.133: icmp_seq=12 ttl=64 time=41.8 ms
64 bytes from 192.168.1.133: icmp_seq=13 ttl=64 time=62.8 ms
64 bytes from 192.168.1.133: icmp_seq=14 ttl=64 time=86.9 ms
64 bytes from 192.168.1.133: icmp_seq=15 ttl=64 time=182 ms
64 bytes from 192.168.1.133: icmp_seq=16 ttl=64 time=205 ms
64 bytes from 192.168.1.133: icmp_seq=17 ttl=64 time=227 ms
64 bytes from 192.168.1.133: icmp_seq=18 ttl=64 time=250 ms
64 bytes from 192.168.1.133: icmp_seq=19 ttl=64 time=273 ms
64 bytes from 192.168.1.133: icmp_seq=20 ttl=64 time=18.7 ms
64 bytes from 192.168.1.133: icmp_seq=21 ttl=64 time=41.6 ms

Both Windows and MacOS do periodic wifi scans to determine their location and those cause a similar behaviour. Google and you should find how to disable it.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.