From owner-freebsd-current Thu Aug 6 10:35:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15583 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:35:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from account.abs.net (account.abs.net [207.114.0.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15573 for ; Thu, 6 Aug 1998 10:35:24 -0700 (PDT) (envelope-from howardl@account.abs.net) Received: (from howardl@localhost) by account.abs.net (8.9.0/8.9.0) id NAA14189; Thu, 6 Aug 1998 13:35:03 -0400 (EDT) From: Howard Leadmon Message-Id: <199808061735.NAA14189@account.abs.net> Subject: 3.0-19980720-SNAP & de full-duplex trouble? To: freebsd-current@FreeBSD.ORG Date: Thu, 6 Aug 1998 13:35:03 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 set 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. Here is what I get from ifconfig: $ ifconfig -a de0: flags=8843 mtu 1500 inet 207.114.0.144 netmask 0xffffff00 broadcast 207.114.0.255 inet 207.114.0.241 netmask 0xffffff00 broadcast 207.114.0.255 inet 207.114.0.242 netmask 0xffffff00 broadcast 207.114.0.255 ether 00:c0:f0:30:0d:ad media: 10baseT/UTP (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP Also looking at dmesg from the reboot, it appears to be in full-duplex: de0: rev 0x22 int a irq 11 on pci0.20.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:30:0d:ad de0: enabling 10baseT port de0: enabling Full Duplex 10baseT port Now the way I did this, was to just set the following in my rc.conf file on the machine: ifconfig_de0="inet 207.114.0.144 netmask 255.255.255.0 media 10baseT/UTP mediao pt 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 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. So does anyone have any ideas? Is the full-duplex option broken in 3.0 current? As this machine is being used for an IRC server, it's seeing a lot of small packets, so running full-duplex would sure cut out a lot of collisions. --- Howard Leadmon - howardl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message