From owner-freebsd-stable Tue Mar 19 13:30:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by hub.freebsd.org (Postfix) with ESMTP id 600E937B419 for ; Tue, 19 Mar 2002 13:30:29 -0800 (PST) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP id GQF37091; Tue, 19 Mar 2002 13:30:28 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Postfix) with ESMTP id B46595D08; Tue, 19 Mar 2002 13:30:25 -0800 (PST) To: Aaron Baugher Cc: David Wolfskill , freebsd-stable@freebsd.org Subject: Re: Network stalls with 4.5 In-reply-to: Your message of "19 Mar 2002 14:32:11 CST." Date: Tue, 19 Mar 2002 13:30:25 -0800 From: "Kevin Oberman" Message-Id: <20020319213025.B46595D08@ptavv.es.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: Aaron Baugher > Date: 19 Mar 2002 14:32:11 -0600 > Sender: owner-freebsd-stable@FreeBSD.ORG > > David Wolfskill writes: > > > You might try doing something as crude as > > > while (1) > > netstat -ni && sleep 10 > > end > > > and use that to see of you're getting errors or collisions durng the > > "stalls". > > Thanks. They've all been up for 20-30 days, and show zero errors or > collisions. Also, we're not having this problem with the Linux or > OpenBSD boxes on the same LAN, so it doesn't seem to be a cabling or > hub problem. Aaron, This may be simple confusion on terminology, but "hub" normally is the term used for a multi-port Ethernet device that acts as a simple repeater with all connections in a common collision domain and all running half-duplex. If this is the case, zero collisions is VERY hard to believe. Collisions will always happen in a half-duplex LAN on a system that does any significant amount of writing to the network. Simple matter of statistics. Is the connecting box a hub (repeater) or a switch (bridge)? If it's a bridge, you should probably be running full-duplex and would ALWAYS have zero collisions as collision detection is disabled in that case. If it's a hub or if the interface is running half-duplex, it's possible that the NIC is defective and that could be the source of the problems. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message