Date: Tue, 12 Jul 2011 11:02:18 -0400 From: "Ross West" <westr@connection.ca> To: <freebsd-net@freebsd.org> Subject: RE: bce packet loss Message-ID: <000b01cc40a4$b17300a0$145901e0$@connection.ca> In-Reply-To: <4E1BE127.9060200@FreeBSD.org> References: <alpine.OSX.2.00.1107042113000.2407@freemac> <20110706201509.GA5559@michelle.cdnetworks.com> <alpine.OSX.2.00.1107070121060.2407@freemac> <20110707174233.GB8702@michelle.cdnetworks.com> <alpine.OSX.2.00.1107072129310.2407@freemac> <5D267A3F22FD854F8F48B3D2B523819385C32D96B7@IRVEXCHCCR01.corp.ad.broadcom.com> <alpine.OSX.2.00.1107082009350.1070@freemac> <5D267A3F22FD854F8F48B3D2B523819385F12FE86B@IRVEXCHCCR01.corp.ad.broadcom.com> <alpine.OSX.2.00.1107112234460.1070@freemac> <4E1BDD3F.4090607@FreeBSD.org> <alpine.OSX.2.00.1107120143390.1070@freemac> <4E1BE127.9060200@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. > > Well one could also say that this sort of thing tends to result from > the, "There is a knob, I MUST twist it!" syndrome. It's a layer 8-9 issue. It results from an auto-negotiation giving a half-duplex connection, and no one noticing until 6 months down the road, then demanding a huge credit from the provider for not selling a full-duplex circuit as was contracted. This happens way more often that you'd think. R.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000b01cc40a4$b17300a0$145901e0$>