Is it normal to so high ping latency via 5GHz wifi channel?
Device on Wifi: 192.168.77.222 (Samsung Galaxy TAB 10.1)
Wifi AP: 192.168.77.158 (RE350)
Ping from PC via Ethernet: 192.168.77.100
ping 192.168.77.222
PING 192.168.77.222 (192.168.77.222) 56(84) bytes of data.
64 bytes from 192.168.77.222: icmp_seq=1 ttl=64 time=81.4 ms
64 bytes from 192.168.77.222: icmp_seq=2 ttl=64 time=108 ms
64 bytes from 192.168.77.222: icmp_seq=3 ttl=64 time=25.5 ms
64 bytes from 192.168.77.222: icmp_seq=4 ttl=64 time=49.3 ms
64 bytes from 192.168.77.222: icmp_seq=5 ttl=64 time=73.3 ms
64 bytes from 192.168.77.222: icmp_seq=6 ttl=64 time=95.3 ms
64 bytes from 192.168.77.222: icmp_seq=7 ttl=64 time=119 ms
64 bytes from 192.168.77.222: icmp_seq=8 ttl=64 time=41.6 ms
64 bytes from 192.168.77.222: icmp_seq=9 ttl=64 time=6.60 ms
64 bytes from 192.168.77.222: icmp_seq=10 ttl=64 time=85.0 ms
64 bytes from 192.168.77.222: icmp_seq=11 ttl=64 time=109 ms
64 bytes from 192.168.77.222: icmp_seq=12 ttl=64 time=34.6 ms
64 bytes from 192.168.77.222: icmp_seq=13 ttl=64 time=58.4 ms
--- 192.168.77.222 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12008ms
rtt min/avg/max/mdev = 6.602/68.276/119.085/33.979 ms
ping 192.168.77.158
PING 192.168.77.158 (192.168.77.158) 56(84) bytes of data.
64 bytes from 192.168.77.158: icmp_seq=1 ttl=64 time=0.602 ms
64 bytes from 192.168.77.158: icmp_seq=2 ttl=64 time=1.21 ms
64 bytes from 192.168.77.158: icmp_seq=3 ttl=64 time=0.621 ms
64 bytes from 192.168.77.158: icmp_seq=4 ttl=64 time=0.576 ms
64 bytes from 192.168.77.158: icmp_seq=5 ttl=64 time=0.488 ms
64 bytes from 192.168.77.158: icmp_seq=6 ttl=64 time=0.413 ms
64 bytes from 192.168.77.158: icmp_seq=7 ttl=64 time=0.778 ms
--- 192.168.77.158 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6078ms
rtt min/avg/max/mdev = 0.413/0.669/1.206/0.243 ms
interference (radar on DFS channels (your wifi will shut down or switch to a different channel, if radar is detected), unshielded USB3, various wifi/bluetooth devices competing for same wifi channels, various other electrical devices (e.g. microwaves), ...)
Usual room of house. No one USB3 device in house. Only 3 wifi device, TV with RC on BT, Only this device in Wifi channels no one other (in 5Ghz, in 2.4GHz - 4-5 routers from neighbourhoods)
Can we check what can be wrong? I have Two RE350 with same latency....
The first step would be to check your configuration, as we cannot do much about hardware and finding flaws in the code is more difficult. Only if it is ruled out that it's not a config thing, then inspecting the code will become necessary.
Most of all we're talking about pinging a smartphone over wireless, phones are using very aggressive powersaving methods (even while it's operating, screen on and actively using the wlan), which makes any kind of ping test pretty much unusable.
Samsung S20+ on OpenWRT-5G network (with disable power saving and Switched Screen On)
# ping 192.168.10.100
PING 192.168.10.100 (192.168.10.100): 56 data bytes
64 bytes from 192.168.10.100: seq=0 ttl=64 time=3.171 ms
64 bytes from 192.168.10.100: seq=1 ttl=64 time=115.702 ms
64 bytes from 192.168.10.100: seq=2 ttl=64 time=2.519 ms
64 bytes from 192.168.10.100: seq=3 ttl=64 time=110.479 ms
64 bytes from 192.168.10.100: seq=4 ttl=64 time=22.422 ms
64 bytes from 192.168.10.100: seq=5 ttl=64 time=3.350 ms
64 bytes from 192.168.10.100: seq=6 ttl=64 time=50.252 ms
64 bytes from 192.168.10.100: seq=7 ttl=64 time=97.298 ms
^C
--- 192.168.10.100 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 2.519/50.649/115.702 ms
Samsung S20+ on OpenWRT (2.4) network (with disable power saving and Switched Screen On)
# ping 192.168.10.99
PING 192.168.10.99 (192.168.10.99): 56 data bytes
64 bytes from 192.168.10.99: seq=0 ttl=64 time=133.716 ms
64 bytes from 192.168.10.99: seq=1 ttl=64 time=82.830 ms
64 bytes from 192.168.10.99: seq=2 ttl=64 time=3.346 ms
64 bytes from 192.168.10.99: seq=3 ttl=64 time=5.227 ms
64 bytes from 192.168.10.99: seq=4 ttl=64 time=90.470 ms
64 bytes from 192.168.10.99: seq=5 ttl=64 time=5.228 ms
64 bytes from 192.168.10.99: seq=6 ttl=64 time=91.754 ms
64 bytes from 192.168.10.99: seq=7 ttl=64 time=131.837 ms
^C
--- 192.168.10.99 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 3.346/68.051/133.716 ms
Ping Windows 10 PC on Ethernet
# ping 192.168.10.2
PING 192.168.10.2 (192.168.10.2): 56 data bytes
64 bytes from 192.168.10.2: seq=0 ttl=128 time=1.578 ms
64 bytes from 192.168.10.2: seq=1 ttl=128 time=1.588 ms
64 bytes from 192.168.10.2: seq=2 ttl=128 time=1.580 ms
64 bytes from 192.168.10.2: seq=3 ttl=128 time=1.202 ms
64 bytes from 192.168.10.2: seq=4 ttl=128 time=1.320 ms
64 bytes from 192.168.10.2: seq=5 ttl=128 time=1.349 ms
64 bytes from 192.168.10.2: seq=6 ttl=128 time=1.198 ms
64 bytes from 192.168.10.2: seq=7 ttl=128 time=1.675 ms
--- 192.168.10.2 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 1.198/1.436/1.675 ms
You forgot to enter the country code. This will limit you to only the barest minimum of tx power usage, as the limit is the common denominator which honors every country in the world, which is either 3 or 6 dBm I believe.
add option country 'your-country-code' to config wifi-device 'radio1' and config wifi-device 'radio0'
Since you are very close (3 meters) to your device, you actually might increase throughput / latency by reducing tx power.
option txpower 'your-tx-power' is missing beneath config wifi-device 'radio1' and config wifi-device 'radio0'
The other day i learned that depending on your mobile devices config, they can employ special power saving methods (maybe even when power-saving mode is off?), which are the cause for high latency and missed message notifications. Check out Proposal to change the default wifi beacon interval from 100 ms to 50 ms
Try to reproduce the ping values with laptop / computer device as client. That way, you will be able to eliminate any errors stemming from cell-phone usage. Also, scanning for wifi and using channel analysis at the same time while doing your ping-test will cause interference.