From owner-freebsd-stable Mon Dec 20 15:36:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id B55A315062 for ; Mon, 20 Dec 1999 15:36:04 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 120CLO-0006aS-00 for stable@freebsd.org; Mon, 20 Dec 1999 18:35:58 -0500 Date: Mon, 20 Dec 1999 18:35:57 -0500 From: Peter Radcliffe To: stable@freebsd.org Subject: Re: xl0 won't autoneg full duplex Message-ID: <19991220183557.F14045@pir.net> Mail-Followup-To: stable@freebsd.org References: <199912202323.KAA13024@lightning.itga.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912202323.KAA13024@lightning.itga.com.au>; from gnb@itga.com.au on Tue, Dec 21, 1999 at 10:23:27AM +1100 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Bond probably said: > I've got a <3Com 3c905B-TX Fast Etherlink XL> plugged into a Cisco > Cat5500 100Mbps switch, and I'm been running various 3.x versions > from 3.0-RELEASE up to the 3.4-RC from 13/12. > This card is happy to run in Full Duplex mode if I force it with ifconfig. If > left to autonegotiate with the switch, the xl0 comes up 100Mbps/half-duplex, > but the switch comes up full duplex. Hence I get lotsa collisions (~20%). Catalysts have had famously bad 100Mbit negotiation. They often won't negotiate correctly with _other_ _cisco_ products, let alone anything else (I had this problem with sparcs plugged into catalysts). Make sure your catalyst is running the most recent software ... it got a bit better. Oh, and next time, go buy foundry switches, they're nicer and cheaper. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message