From owner-freebsd-hardware  Fri Aug  7 13:51:51 1998
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA20027
          for freebsd-hardware-outgoing; Fri, 7 Aug 1998 13:51:51 -0700 (PDT)
          (envelope-from owner-freebsd-hardware@FreeBSD.ORG)
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19730;
          Fri, 7 Aug 1998 13:49:54 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id NAA12171;
          Fri, 7 Aug 1998 13:49:21 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Date: Fri, 7 Aug 1998 13:49:20 -0700 (PDT)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Howard Leadmon <hdl@abs.net>
cc: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG
Subject: Re: 3.0-19980720-SNAP & de driver full-duplex troubles??
In-Reply-To: <199808070545.BAA00539@dll.abs.net>
Message-ID: <Pine.BSF.4.00.9808071348470.15104-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


On Fri, 7 Aug 1998, Howard Leadmon wrote:

>   I loaded up the 3.0 SNAP the other day and things seemed to be going
> well, and then I decided to try and put the DEC-21140 based board I had
> into full-duplex mode.  Needless to say I also put the EtherSwitch it
> was connected to into full-duplex mode (I know the switch handles this
> well as I have a bunch of Solaris boxes running full-duplex on the same
> switch).  
> 
>   My throughput came to a screeching halt, I could barely even FTP any
> files across.  Also even though the machine claimed it was in full-duplex
> mode, it's still showing collisions even after a fresh reboot.

[...]
> ifconfig_de0="inet 207.114.0.144  netmask 255.255.255.0 media 10baseT/UTP
> mediaopt full-duplex"
> 
> 
> So with all the above set, still a netstat -i shows:
> 
> $ netstat -i
> Name  Mtu   Network       Address            Ipkts Ierrs    Opkts Oerrs  Coll
> de0   1500  <Link>      00.c0.f0.30.0d.ad 238593178    11 237898092 5096726
> 4662492
> de0   1500  207.114       u2              238593178    11 237898092 5096726
> 4662492
> 
> 
> So it is seeing collisions, and I can only assume it's runing in half-duplex
> mode, even though everything seems to point to full-duplex.

I'd be thinking of a crossed wire in your drop cable.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message