From owner-freebsd-net@FreeBSD.ORG Fri May 30 15:16:03 2003 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 9672337B401 for ; Fri, 30 May 2003 15:16:03 -0700 (PDT) Received: from praetor.linc-it.com (hardtime.linuxman.net [66.147.26.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3FD243F75 for ; Fri, 30 May 2003 15:16:02 -0700 (PDT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-156-172-64.jan.bellsouth.net [66.156.172.64]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by praetor.linc-it.com (Postfix) with ESMTP id 19F5D15482; Fri, 30 May 2003 17:16:02 -0500 (CDT) Received: by mortis.over-yonder.net (Postfix, from userid 100) id 325A620F28; Fri, 30 May 2003 17:16:00 -0500 (CDT) Date: Fri, 30 May 2003 17:15:59 -0500 From: "Matthew D. Fuller" To: Erwane Breton Message-ID: <20030530221559.GL61246@over-yonder.net> References: <20030529155143.2c39326e.breton@erwane.net> <20030529144639.GI61246@over-yonder.net> <004b01c325f6$2c5cfd20$812a40c1@PETEX31> <20030530182656.08046610.breton@erwane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030530182656.08046610.breton@erwane.net> User-Agent: Mutt/1.4i-fullermd.1 X-Editor: vi X-OS: FreeBSD cc: freebsd-net@freebsd.org Subject: Re: Collision on NIC 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, 30 May 2003 22:16:04 -0000 On Fri, May 30, 2003 at 06:26:56PM +0200 I heard the voice of Erwane Breton, and lo! it spake thus: > > > > > > Well, I don't see the problem. > > > > > > My math says that that's .03% collision rate, which is so deep in the > > > noise as to be practically zero. What do you _think_ it should be? > > > > > Even Mr. Inventor of the ethernet himself regrets calling them collisions because > > that term has a bad ring people unfamiliar with the technological detail. > > > > Pete > > So there are no answers or solutions ? Solution: Do nothing, because nothing is /wrong/. There's nothing to FIX. Move along, nothing to see here. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet"