From owner-freebsd-hackers  Tue May  6 15:04:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA08111
          for hackers-outgoing; Tue, 6 May 1997 15:04:45 -0700 (PDT)
Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA08106
          for <freebsd-hackers@FreeBSD.ORG>; Tue, 6 May 1997 15:04:41 -0700 (PDT)
Received: from zen.nash.org (localhost [127.0.0.1]) by zen.nash.org (8.8.5/8.6.12) with SMTP id RAA10300; Tue, 6 May 1997 17:02:58 -0500 (CDT)
Message-ID: <336FAA92.2C67412E@mcs.com>
Date: Tue, 06 May 1997 17:02:58 -0500
From: Alex Nash <nash@mcs.com>
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386)
MIME-Version: 1.0
To: Archie Cobbs <archie@whistle.com>
CC: archer@lucky.net, freebsd-hackers@FreeBSD.ORG
Subject: Re: option DIAGNOSTIC ?
References: <199705061829.LAA16921@bubba.whistle.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Archie Cobbs wrote:
> > b) My kernel with IPFW panics just after (it seems) a single packet
> >    behind a firewall (ipfw: chain...) -- is it supposed to behave so?
> 
> This is a bug in the ipfw code... will be fixed soon.

I fixed this yesterday.  The fix is available across all three branches
(2.1, 2.2, and -current).

Alex