1 second ping times on a LAN
Bob Edwards
Robert.Edwards at anu.edu.au
Tue Nov 12 17:55:57 EST 2002
Howard Lowndes wrote:
> Can anyone explain why I get this on a LAN:
>
> # ping -n 192.168.40.129
> PING 192.168.40.129 (192.168.40.129) from 192.168.40.1 : 56(84) bytes of
> data.
> 64 bytes from 192.168.40.129: icmp_seq=0 ttl=255 time=999.649 msec
> 64 bytes from 192.168.40.129: icmp_seq=1 ttl=255 time=1.000 sec
> 64 bytes from 192.168.40.129: icmp_seq=2 ttl=255 time=1.000 sec
> 64 bytes from 192.168.40.129: icmp_seq=3 ttl=255 time=1.000 sec
> 64 bytes from 192.168.40.129: icmp_seq=4 ttl=255 time=1.000 sec
> 64 bytes from 192.168.40.129: icmp_seq=5 ttl=255 time=1.000 sec
> 64 bytes from 192.168.40.129: icmp_seq=6 ttl=255 time=1.000 sec
>
> --- 192.168.40.129 ping statistics ---
> 8 packets transmitted, 7 packets received, 12% packet loss
> round-trip min/avg/max/mdev = 999.649/1000.568/1000.789/0.656 ms
>
>
With the very scant information supplied, I can't explain anything. Maybe one
or both machines are loaded. Maybe one machine is running an OS that only
polls for network packets once a second. Who can tell with only this much
information?
Cheers,
Bob Edwards.
More information about the linux
mailing list