From owner-freebsd-hardware Fri Oct 31 20:15:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA27967 for hardware-outgoing; Fri, 31 Oct 1997 20:15:16 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA27950 for ; Fri, 31 Oct 1997 20:15:08 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xRUvm-0002yZ-00; Fri, 31 Oct 1997 20:13:02 -0800 Date: Fri, 31 Oct 1997 20:12:38 -0800 (PST) From: Tom To: David Greenman cc: Mike Tancsa , hardware@freebsd.org Subject: Re: fxp0 and full duplex In-Reply-To: <199711010047.QAA25357@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 31 Oct 1997, David Greenman wrote: > >> No, but trust me. :-) > >> Seriously, there really should be a way to sense the mode when it is in > >>"autoselect" so that it can be displayed with ifconfig. > > > >Wow! Thanks for the quick response... I have a feeling the card is in half > >duplex since I am getting a steady stream of collisions (.4%) ... Its > >connected to a Cisco 4700 FastE port via cross over cable taking a 5Mbit > >ATM feed. I would have thought the collisions would almost be nonexistant.... > > Cisco's don't support NWAY, so you'll have to set the Cisco switch port to > full duplex as well as the fxp. The 4700 is router, not a switch. And yes, you will have to switch it full duplex. > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project Tom (who is constanting annoyed that all 6 of the 10BT ports on the 4500 here are half-duplex only)