From owner-freebsd-questions Fri Nov 14 11:57:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA27884 for questions-outgoing; Fri, 14 Nov 1997 11:57:31 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from mail.websidestory.com (bugs.hitbox.com [209.75.20.4] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA27866 for ; Fri, 14 Nov 1997 11:57:21 -0800 (PST) (envelope-from keric@websidestory.com) Received: from mail.websidestory.com (bugs.hitbox.com [209.75.20.4]) by mail.websidestory.com (8.8.5/8.8.5) with SMTP id MAA19433; Fri, 14 Nov 1997 12:03:40 -0800 (PST) Date: Fri, 14 Nov 1997 12:03:40 -0800 (PST) From: Eric Anderson To: Doug White cc: freebsd-questions@FreeBSD.ORG Subject: Re: Ethernet problem with 2.2.5 and 3C509B In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 14 Nov 1997, Doug White wrote: > > I'm having an interesting problem with a 486DX2/66 running 2.2.5. I have a > > 3Com 3C509B NIC in the box, and during ftp sessions > 15 meg from the box > > over ethernet, the interface quits responding. No ping in or out, no > > nothing. The box becomes totally unreachable. > > > > A netstat reveals an ftp connection in FIN_WAIT1, but I have no idea if > > that is a result or a symptom. an 'ifconfig ep0 up' restores connectivity > > for a short time, but it inevitably dies again. > > > > Any ideas? Bad NIC? (Likely, I need to check.) Obscure issue with 2.2.5 > > and 3C509B's? (Unlikely, methinks.) > > 3Com adapters have been known to die if they receive excessive line noise. > Check out your network connections and cables. Maybe someone else can help me explain this - we're running a whole bunch of Intel 10/100 nics on Pentium Pro/II machines here and every machine to the T has this type of problem: bash-2.01$ netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll fxp0 1500 00.a0.c9.6e.e5.xx 10023234 0 8567462 0 4867357 fxp0 1500 hitbox-netblk xxx 10023234 0 8567462 0 4867357 lo0 16384 50 0 50 0 0 lo0 16384 127 localhost 50 0 50 0 0 bash-2.01$ Of course, these machines are experiencing huge data loads (2+ million hits/day) BUT.. we also have a couple of machines with the 3Com 905 NICs getting the same traffic load and: bash-2.01$ netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll vx0 1500 00.60.97.b5.a3.xx 5855565 0 5020088 0 30 vx0 1500 hitbox-netblk xxx 5855565 0 5020088 0 30 lo0 16384 28 0 28 0 0 lo0 16384 127 localhost 28 0 28 0 0 bash-2.01$ and those figures are consistent with the other 3Com cards we have. Is the 3Com driver just better? None of the cards are in full duplex mode, though I tried with the Intel cards (man fxp) and none of the link1-link2 options work - they just shut the card down. I'm wishing I was back in Solaris country now. =( -- -------------------------------------------------------------------- Eric Anderson Web Side Story * San Diego, CA Director of Network Operations --------------------------------------------------------------------