From owner-freebsd-hackers  Fri Jun 20 17:30:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA04626
          for hackers-outgoing; Fri, 20 Jun 1997 17:30:27 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04621
          for <hackers@freebsd.org>; Fri, 20 Jun 1997 17:30:25 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id RAA06626
	for <hackers@freebsd.org>; Fri, 20 Jun 1997 17:30:18 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd006607; Sat Jun 21 00:30:05 1997
Message-ID: <33AB2047.3F54BC7E@whistle.com>
Date: Fri, 20 Jun 1997 17:28:55 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: 2.2-stable IPFW warning
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

To fix some unrecoverably broken stuff in the firewall
cade it was necessary to implement the same interface through
a different method. this means that the ipfw program must match
the kernel. Hopefully this is the last time this will be needed.

The change has been tested and is in production here at whistle.

I guess other programs that hit the firewall rules (e.g. natd)
might need to be recompiled for the next 2.2 release
I'll make (or help with) the changes if I can track them down..

I don't like making a change like this to -stable, but I couldn't
see a way around this one and it's ramifications are limited to a
small audience.

julian