Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Dec 1999 20:00:18 +1300
From:      Joe Abley <jabley@patho.gen.nz>
To:        Matthew Dillon <dillon@apollo.backplane.com>
Cc:        Poul-Henning Kamp <phk@critter.freebsd.dk>, Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, jlemon@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject:   Re: Odd TCP glitches in new currents
Message-ID:  <19991222200017.A25228@patho.gen.nz>
In-Reply-To: <199912212123.NAA02780@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Dec 21, 1999 at 01:23:05PM -0800
References:  <16589.945810831@critter.freebsd.dk> <199912212123.NAA02780@apollo.backplane.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 21, 1999 at 01:23:05PM -0800, Matthew Dillon wrote:
>     I just rebooted both machines and it didn't fix the problem.  I did a
>     packet trace on both boxes and there does indeed appear to be packet loss.

Sorry if this is stating the obvious, but I've seen more than one
clueful person bitten by this:

  hard-wire your duplex setting on your machine and also on the switch

Even if the switch and NIC appear to auto-negotiate a sensible duplex
setting, I have seen many cases where they will forget for no apparent
reason, usually in the middle of the night just after you have stepped
onto a plane to fly to a different country.

If one end thinks it is full-duplex and the other end thinks it is
half, then late collisions can occur which will not result in MAC-layer
retransmissions from the full-duplex-thinking station -- hence packet
loss.


Joe (possibly #2 in a series of red herrings :)

-- 
Ua lawa küpono ka hakahaka pä o këia pä malule


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991222200017.A25228>