From owner-freebsd-stable  Thu Jan 15 00:02:22 1998
Return-Path: <owner-freebsd-stable>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA12089
          for stable-outgoing; Thu, 15 Jan 1998 00:02:22 -0800 (PST)
          (envelope-from owner-freebsd-stable)
Received: from baklava.alt.net (root@baklava.alt.net [207.14.113.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12065
          for <freebsd-stable@FreeBSD.ORG>; Thu, 15 Jan 1998 00:02:16 -0800 (PST)
          (envelope-from ccaputo@alt.net)
Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.8.5/8.7.3) with SMTP id XAA16576; Wed, 14 Jan 1998 23:58:38 -0800 (PST)
Date: Wed, 14 Jan 1998 23:58:37 -0800 (PST)
From: Chris Caputo <ccaputo@alt.net>
To: Tom <tom@uniserve.com>
cc: freebsd-stable@FreeBSD.ORG
Subject: Re: network performance problems (de0) (resend)
In-Reply-To: <Pine.BSF.3.96.980114231821.15740D-100000@shell.uniserve.com>
Message-ID: <Pine.BSI.3.93.980114235352.16369A-100000@baklava.alt.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 14 Jan 1998, Tom wrote:
> On Wed, 14 Jan 1998, Chris Caputo wrote:
> 
> >    de0: enabling 100baseTX port
> >    de0: enabling Full Duplex 100baseTX port
> ...
> > Any thoughts or suggestions on how to debug this further? 
> 
>   Check the network first.  Is the switch port that the machine is
> connected to set to fullduplex?
>
>   The de driver never used to be capable of fullduplex, so I suspect this
> is the source of your problems.

Thanks for the suggestions. 

The cable, port, and driver have been tested with a FreeBSD 2.1-STABLE
machine and Full Duplex 100baseTX has been confirmed and performance has
corresponded to a working configuration.  The 2.1-STABLE de driver has
been working in full duplex for us for months.

Chris