From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 13:24:19 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5395616A4CE for ; Thu, 8 Jan 2004 13:24:19 -0800 (PST) Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3699A43D48 for ; Thu, 8 Jan 2004 13:24:17 -0800 (PST) (envelope-from adam.mclaurin@gmx.net) Received: from 146-115-126-186.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com ([146.115.126.186] helo=jake) by smtp02.mrf.mail.rcn.net with smtp (Exim 3.35 #4) id 1AehdY-0006fo-00; Thu, 08 Jan 2004 16:24:16 -0500 Date: Thu, 8 Jan 2004 16:24:16 -0500 From: Adam McLaurin To: q_dolan@yahoo.com.au, freebsd-net@freebsd.org Message-Id: <20040108162416.13c13a53.adam.mclaurin@gmx.net> In-Reply-To: <1073530943.77647.90.camel@boxster.onthenet.com.au> References: <20040107151544.6bbab003.adam.mclaurin@gmx.net> <1073530943.77647.90.camel@boxster.onthenet.com.au> Organization: X-Mailer: Sylpheed version 0.9.5-gtk2-20030906 (GTK+ 2.2.4; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Intermittent problems with LAN transfer speeds X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 21:24:19 -0000 On Thu, 08 Jan 2004 13:02:23 +1000 Q wrote: > The first thing you should try is setting the ethernet card to use > autosense. This enables the autosense pulse to be sent to the switch, > without this some passive/unmanaged switches can get very confused and > switch speeds and duplex at seemingly random intervals for a while > before eventually sorting themselves out again. You should only ever > set > speed & duplex manually if you can set it at BOTH ends. > > The easiest way to identify this as the problem is to do a 'netstat > -i' > and check for collisions. If everything on that LAN segment is full > duplex all the time, there should be none. You will most likely have > to > wait for the problem to occur again before the collisions appear. A few things .. First, both speed & duplex are set manualyl at both ends. In fact, I did this more than a year ago as a recommendation to solve this particular problem we're discussing now. In other words, the problem existed before I manually set speed/duplex, and afterwards. Second, the problem doesn't ever sort itself out. If I don't reboot the server, the problem continues indefinitely. Last, here is the output of netstat and ifconfig: http://www.tranceambient.com:8000/public/netstat.output.txt Note: The parts marked with 'x' are indicating my internet IP address, which I am futilely trying to mask. Thanks. -- Adam