>From [email protected] Mon May 10 13:40:55 2010 Received: from shear.ucar.edu (lists.openbsd.org [192.43.244.163]) by lib.oat.com (8.14.3/8.14.3) with ESMTP id o4AHepKb028686 for <[email protected]>; Mon, 10 May 2010 13:40:54 -0400 (EDT) Received: from openbsd.org (localhost.ucar.edu [127.0.0.1]) by shear.ucar.edu (8.14.3/8.14.3) with ESMTP id o4AHg0X8021207; Mon, 10 May 2010 11:42:00 -0600 (MDT) Received: from mail-gw0-f49.google.com (mail-gw0-f49.google.com [74.125.83.49]) by shear.ucar.edu (8.14.3/8.14.3) with ESMTP id o4AHdc5g007664 for <[email protected]>; Mon, 10 May 2010 11:39:39 -0600 (MDT) Received: by gwaa12 with SMTP id a12so2105063gwa.8 for <[email protected]>; Mon, 10 May 2010 10:39:38 -0700 (PDT) Received: by 10.231.146.146 with SMTP id h18mr2473035ibv.27.1273513174288; Mon, 10 May 2010 10:39:34 -0700 (PDT) Received: by 10.231.181.71 with HTTP; Mon, 10 May 2010 10:39:14 -0700 (PDT) Subject: Re: strangely slow OpenBSD server connection To: [email protected]
Patrick Dohman <[email protected]> wrote on Mon, 10 May 2010 10:39:14 -0700 >On Mon, May 10, 2010 at 9:56 AM, Henning Brauer <[email protected]>wrote: > >> >> >> aaaargh! >> >> first, autoneg is pretty damn reliable, the few exceptions are VERY >> old. >> second, taking one side to a fixed speed is calling for trouble. you >> almost certainly end up with one side full- and the otehr half-duplex. >> >> so if your ISP provides ethernet to you asking them whether they set >> the port to auto or fixed is a good idea, but randomly pushing buttons >> is as idiotic as ever. >> >> >Henning all of my respect & I seem to recall you stating this previously. > >I've run into at least five "major" issues in the last six or seven years >that boiled down to auto negotiate. If my memory serves me correctly the >vendors involved were ciscoese, dell & sonicwall. > >Patrick Ditto. I did a major development project which connected to c***** hardware and had nothing but problems with autoneg. Certain other vendors' hardware also would not reliably renegotiate after one end or the other lost power and restarted. This problem occurred with any interface chipset I tried, including recent Intel, etc. geoff steckel omnivore technology
