Code:
C:\Users\Gary>ping 10.0.0.1 -t
Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time=368ms TTL=64
Reply from 10.0.0.1: bytes=32 time=286ms TTL=64
Reply from 10.0.0.1: bytes=32 time=208ms TTL=64
Reply from 10.0.0.1: bytes=32 time=129ms TTL=64
Reply from 10.0.0.1: bytes=32 time=51ms TTL=64
Reply from 10.0.0.1: bytes=32 time=280ms TTL=64
Reply from 10.0.0.1: bytes=32 time=186ms TTL=64
Reply from 10.0.0.1: bytes=32 time=91ms TTL=64
Reply from 10.0.0.1: bytes=32 time=305ms TTL=64
Reply from 10.0.0.1: bytes=32 time=226ms TTL=64
Reply from 10.0.0.1: bytes=32 time=148ms TTL=64
Reply from 10.0.0.1: bytes=32 time=70ms TTL=64
Reply from 10.0.0.1: bytes=32 time=299ms TTL=64
Reply from 10.0.0.1: bytes=32 time=220ms TTL=64
Reply from 10.0.0.1: bytes=32 time=142ms TTL=64
Ping statistics for 10.0.0.1:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 368ms, Average = 200ms
Control-C
^C
C:\Users\Gary>
Above is a ping to the first hop in my network, a wireless access point. As you can clearly see its an absolute pile of ****. What could be causing such terrible responses? I am sitting mere metres away when running this ping fyi.
Any ideas?