What problem is is causing?

sabretooth02 wrote

What problem is is causing?

In practical terms, none.

Technically speaking, it's unacceptable that a router answers ping packets in more than 1ms even when it's CPU is idling.

Inferior and older routers manage to send back ping packets in 1ms or less.

It's just unacceptable, mainly if the OP is a gamer.

By the way, this problem also occurs on the Archer C2 router. Maybe it's something with the MediaTek SOC.

If I ping my UBNT radio through the router connected to one of the LAN ports, its always <1 ms. Also when I ping 192.168.0.1 on wifi, the ping is 1 ms. It's basically via ethernet it spikes.

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.


C:\Users\Lenovo>ping 192.168.0.1 -n 10


Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64


Ping statistics for 192.168.0.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 4ms, Average = 1ms

This is via ethernet, as before.

This is the ping of my RE TL-WA854RE with 40% signal to the Archer C20i

C:\Users\Lenovo>ping 192.168.0.2 -n 10


Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time=6ms TTL=64
Reply from 192.168.0.2: bytes=32 time=5ms TTL=64
Reply from 192.168.0.2: bytes=32 time=1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=2ms TTL=64
Reply from 192.168.0.2: bytes=32 time=1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=6ms TTL=64
Reply from 192.168.0.2: bytes=32 time=2ms TTL=64
Reply from 192.168.0.2: bytes=32 time=4ms TTL=64
Reply from 192.168.0.2: bytes=32 time=7ms TTL=64


Ping statistics for 192.168.0.2:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 7ms, Average = 3ms

Is this good for a 5GHz wifi?

Ping has started…


PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=1.964 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.943 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.829 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.322 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1.817 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=1.869 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=2.102 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=2.097 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=2.079 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=2.237 ms


--- 192.168.0.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.817/2.026/2.322/0.162 ms