From owner-freebsd-isp Sun Sep 10 13:10: 5 2000 Delivered-To: freebsd-isp@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 53A6437B424 for ; Sun, 10 Sep 2000 13:10:02 -0700 (PDT) Received: from confusion.net (user-2ivebf7.dialup.mindspring.com [165.247.45.231]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id QAA22637; Sun, 10 Sep 2000 16:09:50 -0400 (EDT) Message-ID: <39BBEA84.5F306051@confusion.net> Date: Sun, 10 Sep 2000 16:09:40 -0400 From: Laurence Berland X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: sthaug@nethelp.no Cc: mike@mikesweb.com, wizard@sybaweb.co.za, freebsd-isp@FreeBSD.ORG Subject: Re: NIC settings References: <39BBE2A6.76BA1145@confusion.net> <15790.968614746@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Let's see if this is the right way to describe the process 1. packet comes across t1 bound for local ethernet. 2. the router examines the packet, determines it should go out over ethernet. 3. the router uses csma/cd and gets one of the followng a) line in use, so wait for it free b) line free, transmits frame successfully c) line free, transmits frame, collision occurs so back off a random time and retry. C is the one we're interested in. I don't see how it would increase the utilization of the T1 at all (as the author to whom I originally replied alluded) sthaug@nethelp.no wrote: > > > Should not the router on the T1 be performing some sort of cacheing so > > that packets don't get retransmitted across the T1 every time a > > collision occurs? > > Um, packets *don't* get retransmitted across the T1 every time a > collision occurs. In fact packets don't even get *to* the router's > Ethernet port until the collision is resolved. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message