R500 Large Ping & unstable path to client

[itdept_head_me]

Am seeing massive "ping delays & drops to  clients  under R500 AP.. .sometimes.

Basically the APs' operate in a very polluted hostile environment.


Client is windows ,traffic is next to nothing.


172.20.1.121

802.11b/g/n
-66 dBm
46 dB
Excellent



ping to the AP


ping 172.20.0.6
PING 172.20.0.6 (172.20.0.6): 56 data bytes
64 bytes from 172.20.0.6: icmp_seq=0 ttl=63 time=6.982 ms
64 bytes from 172.20.0.6: icmp_seq=1 ttl=63 time=6.812 ms
64 bytes from 172.20.0.6: icmp_seq=2 ttl=63 time=6.685 ms
64 bytes from 172.20.0.6: icmp_seq=3 ttl=63 time=6.707 ms

ping to the client

64 bytes from 172.20.1.63: icmp_seq=967 ttl=63 time=108.552 ms
Request timeout for icmp_seq 968
Request timeout for icmp_seq 969
Request timeout for icmp_seq 970
64 bytes from 172.20.1.63: icmp_seq=969 ttl=63 time=2324.465 ms
64 bytes from 172.20.1.63: icmp_seq=970 ttl=63 time=1399.448 ms
64 bytes from 172.20.1.63: icmp_seq=971 ttl=63 time=395.006 ms
64 bytes from 172.20.1.63: icmp_seq=972 ttl=63 time=528.905 ms
64 bytes from 172.20.1.63: icmp_seq=973 ttl=63 time=212.009 ms
64 bytes from 172.20.1.63: icmp_seq=974 ttl=63 time=757.311 ms
64 bytes from 172.20.1.63: icmp_seq=975 ttl=63 time=276.469 ms
64 bytes from 172.20.1.63: icmp_seq=976 ttl=63 time=1269.509 ms
64 bytes from 172.20.1.63: icmp_seq=977 ttl=63 time=267.469 ms
64 bytes from 172.20.1.63: icmp_seq=978 ttl=63 time=1972.205 ms
64 bytes from 172.20.1.63: icmp_seq=979 ttl=63 time=970.159 ms
64 bytes from 172.20.1.63: icmp_seq=980 ttl=63 time=55.247 ms
64 bytes from 172.20.1.63: icmp_seq=981 ttl=63 time=394.299 ms
64 bytes from 172.20.1.63: icmp_seq=982 ttl=63 time=617.992 ms
64 bytes from 172.20.1.63: icmp_seq=983 ttl=63 time=536.143 ms
64 bytes from 172.20.1.63: icmp_seq=984 ttl=63 time=48.595 ms
64 bytes from 172.20.1.63: icmp_seq=985 ttl=63 time=1613.516 ms





My main issue is why it is classed as "excellent"?

is there any way to get counters on resends/drops, that sort of thing?
packet loss?