Thread: For enyone on Be* on fast path
View Single Post
Old 10-02-2008, 22:14   #7
dragon
Inactive
 
Join Date: Jan 2004
Posts: 3,898
dragon has reached the bronze age
dragon has reached the bronze agedragon has reached the bronze agedragon has reached the bronze agedragon has reached the bronze agedragon has reached the bronze agedragon has reached the bronze agedragon has reached the bronze agedragon has reached the bronze agedragon has reached the bronze agedragon has reached the bronze age
Re: For enyone on Be* on fast path
Heres mine from BT broadband.

C:\Users\Dragon>ping 82.133.85.65 -n 10

Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=61ms TTL=51
Reply from 82.133.85.65: bytes=32 time=23ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=298ms TTL=51
Reply from 82.133.85.65: bytes=32 time=16ms TTL=51
Reply from 82.133.85.65: bytes=32 time=130ms TTL=51
Reply from 82.133.85.65: bytes=32 time=94ms TTL=51
Reply from 82.133.85.65: bytes=32 time=17ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=57ms TTL=51

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

C:\Users\Dragon>

Although

C:\Users\Dragon>ping 192.168.1.1 -n 10

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=18ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=27ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=15ms TTL=255
Reply from 192.168.1.1: bytes=32 time=87ms TTL=255
Reply from 192.168.1.1: bytes=32 time=60ms TTL=255

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

C:\Users\Dragon>

Quite a bit of that variation can be attributed to my UPA (powerline) adaptors.

---------- Post added at 23:14 ---------- Previous post was at 22:57 ----------

C:\Users\Dragon>ping 192.168.1.1 -n 10

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=21ms TTL=255
Reply from 192.168.1.1: bytes=32 time=8ms TTL=255
Reply from 192.168.1.1: bytes=32 time=11ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=3ms TTL=255
Reply from 192.168.1.1: bytes=32 time=11ms TTL=255
Reply from 192.168.1.1: bytes=32 time=29ms TTL=255

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

C:\Users\Dragon>ping 82.133.85.65 -n 10

Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=17ms TTL=51
Reply from 82.133.85.65: bytes=32 time=17ms TTL=51
Reply from 82.133.85.65: bytes=32 time=24ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=19ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=16ms TTL=51
Reply from 82.133.85.65: bytes=32 time=15ms TTL=51
Reply from 82.133.85.65: bytes=32 time=15ms TTL=51
Reply from 82.133.85.65: bytes=32 time=15ms TTL=51

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

C:\Users\Dragon>

That made a slight difference (Swapped the UPA adaptors for a pair of homeplugs I had handy)
dragon is offline   Reply With Quote