From owner-freebsd-questions@FreeBSD.ORG Mon Mar 31 10:20:49 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CB0F37B401 for ; Mon, 31 Mar 2003 10:20:49 -0800 (PST) Received: from grumpy.dyndns.org (user-24-214-34-52.knology.net [24.214.34.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A8F843F93 for ; Mon, 31 Mar 2003 10:20:48 -0800 (PST) (envelope-from dkelly@grumpy.dyndns.org) Received: from grumpy.dyndns.org (localhost [127.0.0.1]) by grumpy.dyndns.org (8.12.8/8.12.7) with ESMTP id h2VIKl2T061884; Mon, 31 Mar 2003 12:20:47 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Received: (from dkelly@localhost) by grumpy.dyndns.org (8.12.8/8.12.7/Submit) id h2VIKkcU061883; Mon, 31 Mar 2003 12:20:46 -0600 (CST) Date: Mon, 31 Mar 2003 12:20:46 -0600 From: David Kelly To: "Jack L. Stone" Message-ID: <20030331182046.GC61524@grumpy.dyndns.org> References: <20030331143804.GG322@ns1.webwarrior.net> <3.0.5.32.20030331082034.01414bf8@sage-one.net> <20030331143804.GG322@ns1.webwarrior.net> <3.0.5.32.20030331103405.013e5298@sage-one.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3.0.5.32.20030331103405.013e5298@sage-one.net> User-Agent: Mutt/1.4.1i cc: FreeBSD-Questions@freebsd.org Subject: Re: Interface collisions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 18:20:50 -0000 On Mon, Mar 31, 2003 at 10:34:05AM -0600, Jack L. Stone wrote: [...] > > Also, I agree that the collisions are very small and were cached by the > switch, not lost necessarily. However, the sudden appearance over the past > 2-3 days indicates a change that is not for the better and more concerned > about the trend. Not "cached by the switch" else your rl driver would not have known about it. The rl driver logged the "collision" because it started sending a packet and was not able to copy it 100% in real time so it concluded somebody else was transmitting at the same time. If the card is configured in full duplex mode it should not be verifying copy of its own data when sending, by definition. Unless there is some sort of out-of-band communications between ethernet ports operating via full duplex. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.