[plug] Ping Times

Justin justin at inwa.com.au
Mon Aug 20 21:00:39 WST 2001


Hello All

Just a quick question as a matter of idle interest.

I have a Debian box that Masqs for a small windows network - using 2.2.17
When i ping an outside address from a W2k box on the internal network, the 
ping i get is smaller than the ping i get on the linux box - consistently 
by about 10ms (not huge i know).

If you have an idea or are interested in any slight way, then here are some 
numbers (down a little).. Otherwise enjoy the rest of you emails.

I understand this is probably of no real consequence - I just find it a 
little interesting that the Linux box was not the quicker of the two! Is it 
a 2.2.17 issue? Or is Winblows using some trick? Or could it be something 
to do with my setup?

Thanks for any thoughts.

Justin

W2k
Pinging 203.59.134.51 with 32 bytes of data:
Reply from 203.59.134.51: bytes=32 time=60ms TTL=123
Reply from 203.59.134.51: bytes=32 time=60ms TTL=123
Reply from 203.59.134.51: bytes=32 time=51ms TTL=123
Reply from 203.59.134.51: bytes=32 time=50ms TTL=123
Reply from 203.59.134.51: bytes=32 time=80ms TTL=123
Reply from 203.59.134.51: bytes=32 time=60ms TTL=123
Reply from 203.59.134.51: bytes=32 time=60ms TTL=123
Reply from 203.59.134.51: bytes=32 time=70ms TTL=123
Reply from 203.59.134.51: bytes=32 time=50ms TTL=123
Reply from 203.59.134.51: bytes=32 time=50ms TTL=123
Reply from 203.59.134.51: bytes=32 time=70ms TTL=123
Reply from 203.59.134.51: bytes=32 time=61ms TTL=123
Reply from 203.59.134.51: bytes=32 time=60ms TTL=123
Reply from 203.59.134.51: bytes=32 time=80ms TTL=123
Reply from 203.59.134.51: bytes=32 time=50ms TTL=123
Reply from 203.59.134.51: bytes=32 time=60ms TTL=123
Reply from 203.59.134.51: bytes=32 time=60ms TTL=123
Reply from 203.59.134.51: bytes=32 time=50ms TTL=123
Reply from 203.59.134.51: bytes=32 time=50ms TTL=123
Reply from 203.59.134.51: bytes=32 time=50ms TTL=123

Ping statistics for 203.xx.xx.51:
     Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
     Minimum = 50ms, Maximum =  100ms, Average =  61ms

Linux box
PING 203.59.134.51 (203.59.134.51): 56 data bytes
64 bytes from 203.59.134.51: icmp_seq=0 ttl=124 time=76.8 ms
64 bytes from 203.59.134.51: icmp_seq=1 ttl=124 time=70.4 ms
64 bytes from 203.59.134.51: icmp_seq=2 ttl=124 time=72.5 ms
64 bytes from 203.59.134.51: icmp_seq=3 ttl=124 time=71.3 ms
64 bytes from 203.59.134.51: icmp_seq=4 ttl=124 time=73.0 ms
64 bytes from 203.59.134.51: icmp_seq=5 ttl=124 time=71.8 ms
64 bytes from 203.59.134.51: icmp_seq=6 ttl=124 time=72.0 ms
64 bytes from 203.59.134.51: icmp_seq=7 ttl=124 time=77.9 ms
64 bytes from 203.59.134.51: icmp_seq=8 ttl=124 time=74.6 ms
64 bytes from 203.59.134.51: icmp_seq=9 ttl=124 time=74.9 ms
64 bytes from 203.59.134.51: icmp_seq=10 ttl=124 time=79.0 ms
64 bytes from 203.59.134.51: icmp_seq=11 ttl=124 time=77.6 ms
64 bytes from 203.59.134.51: icmp_seq=12 ttl=124 time=79.1 ms
64 bytes from 203.59.134.51: icmp_seq=13 ttl=124 time=74.3 ms
64 bytes from 203.59.134.51: icmp_seq=14 ttl=124 time=76.8 ms
64 bytes from 203.59.134.51: icmp_seq=15 ttl=124 time=77.1 ms
64 bytes from 203.59.134.51: icmp_seq=16 ttl=124 time=77.6 ms
64 bytes from 203.59.134.51: icmp_seq=17 ttl=124 time=75.5 ms
64 bytes from 203.59.134.51: icmp_seq=18 ttl=124 time=74.3 ms
64 bytes from 203.59.134.51: icmp_seq=19 ttl=124 time=81.0 ms

--- 203.59.134.51 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 70.4/75.3/81.0 ms




More information about the plug mailing list