From owner-freebsd-current@FreeBSD.ORG Wed Aug 11 23:00:36 2004 Return-Path: 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 6BE2716A4D5; Wed, 11 Aug 2004 23:00:36 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id C366943D5E; Wed, 11 Aug 2004 23:00:25 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.34 (FreeBSD)) id 1Bv24x-000JPM-1z; Wed, 11 Aug 2004 16:00:19 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16666.42242.552955.635999@ran.psg.com> Date: Wed, 11 Aug 2004 16:00:18 -0700 To: Robert Watson References: <16666.37963.904734.842647@ran.psg.com> cc: FreeBSD Current 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 23:00:36 -0000 >> 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 bingo! thanks. randy