fizikz
DD-WRT User
Joined: 10 Nov 2016
Posts: 186
|
 Posted: Tue Dec 29, 2020 3:10 Post subject: Asymmetric ping results? |
 |
From my client (PC) to the AP, I'm getting expected ping results:
| Code: | $ ping 192.168.2.2
PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.
64 bytes from 192.168.2.2: icmp_seq=1 ttl=64 time=1.16 ms
64 bytes from 192.168.2.2: icmp_seq=2 ttl=64 time=1.37 ms
64 bytes from 192.168.2.2: icmp_seq=3 ttl=64 time=0.718 ms
64 bytes from 192.168.2.2: icmp_seq=4 ttl=64 time=1.00 ms
64 bytes from 192.168.2.2: icmp_seq=5 ttl=64 time=1.75 ms
64 bytes from 192.168.2.2: icmp_seq=6 ttl=64 time=0.994 ms
64 bytes from 192.168.2.2: icmp_seq=7 ttl=64 time=1.29 ms
64 bytes from 192.168.2.2: icmp_seq=8 ttl=64 time=1.43 ms
64 bytes from 192.168.2.2: icmp_seq=9 ttl=64 time=1.77 ms
64 bytes from 192.168.2.2: icmp_seq=10 ttl=64 time=2.63 ms
64 bytes from 192.168.2.2: icmp_seq=11 ttl=64 time=1.02 ms
64 bytes from 192.168.2.2: icmp_seq=12 ttl=64 time=1.20 ms
64 bytes from 192.168.2.2: icmp_seq=13 ttl=64 time=0.723 ms
64 bytes from 192.168.2.2: icmp_seq=14 ttl=64 time=0.778 ms
64 bytes from 192.168.2.2: icmp_seq=15 ttl=64 time=0.754 ms
64 bytes from 192.168.2.2: icmp_seq=16 ttl=64 time=1.11 ms
64 bytes from 192.168.2.2: icmp_seq=17 ttl=64 time=2.62 ms
64 bytes from 192.168.2.2: icmp_seq=18 ttl=64 time=1.19 ms
64 bytes from 192.168.2.2: icmp_seq=19 ttl=64 time=1.18 ms
64 bytes from 192.168.2.2: icmp_seq=20 ttl=64 time=2.53 ms
^C
--- 192.168.2.2 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19115ms
rtt min/avg/max/mdev = 0.718/1.361/2.629/0.590 ms
|
But pinging from the AP (via ssh) to the client, the latency and consistency (jitter?) are way worse!
| Code: | # ping 192.168.2.8
PING 192.168.2.8 (192.168.2.8): 56 data bytes
64 bytes from 192.168.2.8: seq=0 ttl=64 time=0.983 ms
64 bytes from 192.168.2.8: seq=1 ttl=64 time=138.885 ms
64 bytes from 192.168.2.8: seq=2 ttl=64 time=54.834 ms
64 bytes from 192.168.2.8: seq=3 ttl=64 time=86.900 ms
64 bytes from 192.168.2.8: seq=4 ttl=64 time=3.383 ms
64 bytes from 192.168.2.8: seq=5 ttl=64 time=136.482 ms
64 bytes from 192.168.2.8: seq=6 ttl=64 time=414.051 ms
64 bytes from 192.168.2.8: seq=7 ttl=64 time=333.360 ms
64 bytes from 192.168.2.8: seq=8 ttl=64 time=246.907 ms
64 bytes from 192.168.2.8: seq=9 ttl=64 time=0.853 ms
64 bytes from 192.168.2.8: seq=10 ttl=64 time=102.868 ms
64 bytes from 192.168.2.8: seq=11 ttl=64 time=110.850 ms
64 bytes from 192.168.2.8: seq=12 ttl=64 time=27.497 ms
64 bytes from 192.168.2.8: seq=13 ttl=64 time=354.912 ms
64 bytes from 192.168.2.8: seq=14 ttl=64 time=438.811 ms
64 bytes from 192.168.2.8: seq=15 ttl=64 time=179.494 ms
64 bytes from 192.168.2.8: seq=16 ttl=64 time=91.684 ms
64 bytes from 192.168.2.8: seq=17 ttl=64 time=4.119 ms
64 bytes from 192.168.2.8: seq=18 ttl=64 time=219.080 ms
64 bytes from 192.168.2.8: seq=19 ttl=64 time=436.023 ms
64 bytes from 192.168.2.8: seq=20 ttl=64 time=456.344 ms
^C
--- 192.168.2.8 ping statistics ---
21 packets transmitted, 21 packets received, 0% packet loss
round-trip min/avg/max = 0.853/182.777/456.344 ms
|
What's going on? |
|
