From owner-freebsd-stable Fri Nov 14 06:37:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA02855 for stable-outgoing; Fri, 14 Nov 1997 06:37:30 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA02816 for ; Fri, 14 Nov 1997 06:36:57 -0800 (PST) (envelope-from nash@Venus.mcs.net) Received: from Venus.mcs.net (nash@Venus.mcs.net [192.160.127.92]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id IAA06344; Fri, 14 Nov 1997 08:35:00 -0600 (CST) Received: from localhost (nash@localhost) by Venus.mcs.net (8.8.7/8.8.2) with SMTP id IAA20704; Fri, 14 Nov 1997 08:34:54 -0600 (CST) Date: Fri, 14 Nov 1997 08:34:54 -0600 (CST) From: Alex Nash To: Studded cc: FreeBSD Stable List Subject: Re: Serious problem with ipfw in 11/10 Snap In-Reply-To: <199711140725.XAA05912@mail.san.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 13 Nov 1997, Studded wrote: [...] > persisted even after a flush, so it was definitely a problem with the code. [...] > He suggested that if this happens again, he's going to put > up a note on the server for the 40,000 users we get every day apologizing for > the outage, and explaining that they can blame it on FreeBSD. [...] > I've two reasons for writing this. The most important is to notify whoever > is working on this part of the code, and helpfully make sure it doesn't happen > again. This code hasn't changed on the 2.2 branch since August 23. The same code that's in 2.2.5 is in the 11/10 snap (that you claim is broken) and the 11/11 snap (that you claim is fixed). Alex