Re: [SLUG] Re: 1 second ping times on a LAN

[Jon Biddell]

> > 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

I would hazard a guess that you have one or both NICs set to auto-negotiate, combined with a 3COM switch that is fscked as far as auto-negotiation goes...

No excuse, on a stable fixed network, not to hard-code the speed / duplex... Unless, like my *^&^&^*( Intel Pro/100+ you can only get 100 half duplex under Linux...

Grrrrr

Jon

--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug