PING 192.168.1.1 (192.168.1.1): 48 data bytes
56 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=21.018 ms
56 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.171 ms
56 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.957 ms
56 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.715 ms
56 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.149 ms
56 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=3.833 ms
56 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=3.682 ms
56 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=3.705 ms
^C--- 192.168.1.1 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.149/5.279/21.018/6.051 ms
Is this acceptable? For a time I'd consistently get 1.XXX ms of ping to the router, now it's more like 3.XXX.
Should I set up subnets? Should I enable QoS on the individual devices other than the router? I've never understood why QoS is an option for switches, access points, and even Windows. _________________ Google is Spyware
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Sun Nov 14, 2021 9:26 Post subject:
Hi there.
So those ping reply times look quite high to me.
A 56 byte ping on my LAN from a wired connection to say a wifi client results in 2ms
If I ping the router itself from a wired connection, its 1ms.
I dont have any QOS setup anywhere.
There are many reasons for a high ping like firewalls, general configs or high bandwidth consuming services running on some machines, but not limited to that.
If you just search around the web you will maybe get a better idea, and then since you know the network you be able to try to improve that.
WLAN is a shared medium and if there is any load on the used WLAN channels then the WLAN latency increases.
This does not even have to be load from own clients, it can also be the neighbor who uses the same frequency range.
The latency can quickly increase to 25-50ms (but you need a lot of load / interference for this).
3ms are perfectly fine but that will be much more if, as I said, there is somehow load on the WLAN
as long as the wifi is not operated in a completely interference-free environment, there will be no consistent latency.
These pings are over wifi from a free dedicated channel.
PING 192.168.1.1 (192.168.1.1): 48 data bytes
56 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=24.754 ms
56 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.143 ms
56 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.008 ms
56 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=12.207 ms
56 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.167 ms
56 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.098 ms
56 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=6.066 ms
56 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.078 ms
56 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.015 ms
^C--- 192.168.1.1 ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.008/5.504/24.754/7.696 ms
I just got this. I guess it is acceptable. _________________ Google is Spyware
Just updated to the latest firmware. Pinging my desktop from my laptop (in the same room on the same access point) gives me this shit:
Code:
PING 192.168.1.101 (192.168.1.101): 48 data bytes
56 bytes from 192.168.1.101: icmp_seq=0 ttl=64 time=140.150 ms
56 bytes from 192.168.1.101: icmp_seq=1 ttl=64 time=184.513 ms
56 bytes from 192.168.1.101: icmp_seq=2 ttl=64 time=4.180 ms
56 bytes from 192.168.1.101: icmp_seq=3 ttl=64 time=64.422 ms
56 bytes from 192.168.1.101: icmp_seq=4 ttl=64 time=108.848 ms
56 bytes from 192.168.1.101: icmp_seq=5 ttl=64 time=152.552 ms
56 bytes from 192.168.1.101: icmp_seq=6 ttl=64 time=195.534 ms
56 bytes from 192.168.1.101: icmp_seq=7 ttl=64 time=1.492 ms
56 bytes from 192.168.1.101: icmp_seq=8 ttl=64 time=75.588 ms
56 bytes from 192.168.1.101: icmp_seq=9 ttl=64 time=118.386 ms
^C--- 192.168.1.101 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.492/104.566/195.534/64.496 ms
No idea why. In fact for a time I saw a pattern: ~1ms, ~50ms, ~120ms, ~1ms, ~50ms, ~120ms, etc.
Cisco access point (does dd-wrt run on the netgear access points, i.e. WAX214)? _________________ Google is Spyware