From owner-freebsd-current@FreeBSD.ORG  Wed Aug 11 21:56:01 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F1DAF16A4CF
	for <freebsd-current@freebsd.org>;
	Wed, 11 Aug 2004 21:56:00 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A4A2C43D1D
	for <freebsd-current@freebsd.org>;
	Wed, 11 Aug 2004 21:56:00 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i7BLsNRU030801;
	Wed, 11 Aug 2004 17:54:23 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)i7BLsNO7030798;
	Wed, 11 Aug 2004 17:54:23 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Wed, 11 Aug 2004 17:54:23 -0400 (EDT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Randy Bush <randy@psg.com>
In-Reply-To: <16666.37963.904734.842647@ran.psg.com>
Message-ID: <Pine.NEB.3.96L.1040811175316.28766B-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: ipfw
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Aug 2004 21:56:01 -0000


On Wed, 11 Aug 2004, Randy Bush wrote:

> ipfw seems to be starting in some strange state where it has loaded my
> ruleset but does not really process it.  everything ends up in
> unreachable.  if i run `ipfw -q /etc/ipfw.rules`, the same command set
> that's in /etc/rc.conf, it takes off as expected. 

The recent addition of O_ANTISPOOF renumbered the IPFW rule operations, so
if you're using a newer kernel and an older user space, /sbin/ipfw will
think the rules mean one thing, but the kernel will think they mean
another.  The miscreant has been convinced that this is a bad idea (always
append!) but since the damage was done we decided not to thrash the
operator numbers again. 

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Principal Research Scientist, McAfee Research