From owner-freebsd-net@FreeBSD.ORG Tue Jul 12 05:52:42 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id B68FD1065673; Tue, 12 Jul 2011 05:52:42 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-4.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 6F9C817A37E; Tue, 12 Jul 2011 05:52:40 +0000 (UTC) Message-ID: <4E1BE127.9060200@FreeBSD.org> Date: Mon, 11 Jul 2011 22:52:39 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: Charles Sprickman References: <20110706201509.GA5559@michelle.cdnetworks.com> <20110707174233.GB8702@michelle.cdnetworks.com> <5D267A3F22FD854F8F48B3D2B523819385C32D96B7@IRVEXCHCCR01.corp.ad.broadcom.com> <5D267A3F22FD854F8F48B3D2B523819385F12FE86B@IRVEXCHCCR01.corp.ad.broadcom.com> <4E1BDD3F.4090607@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.2pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: YongHyeon PYUN , "freebsd-net@freebsd.org" , David Christensen , David Christensen Subject: Re: bce packet loss X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2011 05:52:42 -0000 On 07/11/2011 22:47, Charles Sprickman wrote: > On Mon, 11 Jul 2011, Doug Barton wrote: > >> On 07/11/2011 21:09, Charles Sprickman wrote: >>> I've had it hammered into my brain over the years that for servers it's >>> always best to set link speed and duplex manually at both ends to remove >>> any possible issues with link negotiation. >> >> That hasn't been the right thing to do for at least 8 years or so, >> probably 10 or more. >> >> Yes, back in the 90's when all of this stuff was still new it was not >> uncommon to have autonegotiation issues, but any even sort of modern >> hardware (on either side of the link) will do better with auto than not. > > Some of us still work at places where the hardware is 10 years old, you > know. :) True ... hence my careful specification of "sort of modern." :) > I do still see fixed setups in service provider handoffs - for example > this colo, Level3 and Hurricane. Also all our metro ethernet stuff > specifies a fixed configuration. > > From what I can gather, this seems to be the standard practice in that > space, but then again you're supposed to be plugging into equipment that > wouldn't have the buffer issues that a $450 Dell switch would have. Well one could also say that this sort of thing tends to result from the, "There is a knob, I MUST twist it!" syndrome. > The rule I recall is never do autoneg on one side and fixed on the > other, that more often than not will end up in a duplex mismatch. Yes, that's definitely true, and I should have mentioned it. Whatever you do on one side (auto/manual) you must also do on the other. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/