From owner-freebsd-current@FreeBSD.ORG Tue Sep 7 16:54:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E329616A4CE for ; Tue, 7 Sep 2004 16:54:56 +0000 (GMT) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.FreeBSD.org (Postfix) with SMTP id 7697443D55 for ; Tue, 7 Sep 2004 16:54:55 +0000 (GMT) (envelope-from sthaug@nethelp.no) Received: (qmail 83359 invoked by uid 1001); 7 Sep 2004 16:54:53 -0000 To: freebsd@jdc.parodius.com From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 7 Sep 2004 09:18:52 -0700" References: <20040907161851.GA67411@parodius.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 07 Sep 2004 18:54:53 +0200 Message-ID: <83357.1094576093@bizet.nethelp.no> cc: freebsd-current@freebsd.org Subject: Re: BETA3 showstoppers (read: critical bugs) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2004 16:54:57 -0000 > I can confirm Brandon's comments (re: 802.3 speed/duplex negotiation not > working properly with Cisco equipment). At Best, we had to force duplex > and speed on both our Catalysts and our BSD boxes, otherwise, mysterious > problems would occur (slow transfer rates in one direction, input or > output errors, etc.). I'm sure Matt Dillon can attest to this as well. We had lots of such problems with older Catalysts. Newer Catalysts seem to mostly autonegotiate just fine. We tend to leave the ports in auto mode towards hosts, and set speed/duplex explicitly between network equipment. Steinar Haug, Nethelp consulting, sthaug@nethelp.no