From owner-freebsd-hardware  Fri Oct 31 16:47:16 1997
Return-Path: <owner-freebsd-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA16823
          for hardware-outgoing; Fri, 31 Oct 1997 16:47:16 -0800 (PST)
          (envelope-from owner-freebsd-hardware)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA16813
          for <hardware@FreeBSD.ORG>; Fri, 31 Oct 1997 16:47:02 -0800 (PST)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA25357;
	Fri, 31 Oct 1997 16:47:58 -0800 (PST)
Message-Id: <199711010047.QAA25357@implode.root.com>
To: Mike Tancsa <mike@sentex.net>
cc: hardware@FreeBSD.ORG
Subject: Re: fxp0 and full duplex 
In-reply-to: Your message of "Fri, 31 Oct 1997 19:38:20 EST."
             <3.0.2.32.19971031193820.0266e950@sentex.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 31 Oct 1997 16:47:58 -0800
Sender: owner-freebsd-hardware@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>   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.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project