From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 13:48:28 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 4A6AF16A4CE for ; Fri, 9 Jan 2004 13:48:28 -0800 (PST) Received: from ints.mail.pike.ru (ints.mail.pike.ru [195.9.45.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62AD743D1D for ; Fri, 9 Jan 2004 13:48:25 -0800 (PST) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 62044 invoked from network); 9 Jan 2004 22:04:07 -0000 Received: from babolo.ru (HELO cicuta.babolo.ru) (194.58.226.160) by ints.mail.pike.ru with SMTP; 9 Jan 2004 22:04:07 -0000 Received: (nullmailer pid 1070 invoked by uid 136); Fri, 09 Jan 2004 21:48:26 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20040108162416.13c13a53.adam.mclaurin@gmx.net> To: Adam McLaurin Date: Sat, 10 Jan 2004 00:48:26 +0300 (MSK) From: "."@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <1073684906.433504.1069.nullmailer@cicuta.babolo.ru> cc: freebsd-net@freebsd.org cc: q_dolan@yahoo.com.au 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: Fri, 09 Jan 2004 21:48:28 -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. Does ifconfig xx down; ifconfig xx up helps? Can be packet loss triggered by a lot of small packets on this interface?