From owner-freebsd-net Mon Mar 19 13:41:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.157]) by hub.freebsd.org (Postfix) with ESMTP id 2F47337B736 for ; Mon, 19 Mar 2001 13:41:17 -0800 (PST) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.11.1/8.11.1) id f2JLep198681; Tue, 20 Mar 2001 00:40:51 +0300 (MSK) (envelope-from yar) Date: Tue, 20 Mar 2001 00:40:51 +0300 From: Yar Tikhiy To: Garrett Wollman Cc: freebsd-net@FreeBSD.ORG Subject: Re: A few nasty bugs in the networking code Message-ID: <20010320004051.N43447@comp.chem.msu.su> References: <20010319203104.L43447@comp.chem.msu.su> <200103191732.SAA85848@info.iet.unipi.it> <20010319205902.M43447@comp.chem.msu.su> <200103191808.NAA94850@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103191808.NAA94850@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Mon, Mar 19, 2001 at 01:08:32PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Garrett, On Mon, Mar 19, 2001 at 01:08:32PM -0500, Garrett Wollman wrote: > > I have taken a look at all of these and your suggested fixes appear to > be correct in concept. I have not tested any of them, however. As for me, I can see a fixed system work perfectly for months. It was an unofficial Cisco ISL implementation that triggered all the bugs, and after fixing them I got a router that has been up for a couple of months right now and relays 20 to 30 Mbit/sec in the peak hours each weekday. SY, Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message