From owner-freebsd-current@FreeBSD.ORG Thu Aug 19 16:16:51 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 3353F16A4CE; Thu, 19 Aug 2004 16:16:51 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D00443D55; Thu, 19 Aug 2004 16:16:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.2.73] (cpe.125.wat.v126.packetworks.net [64.235.97.125] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i7JGHOB2069915; Thu, 19 Aug 2004 10:17:24 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4124D1D4.5080307@samsco.org> Date: Thu, 19 Aug 2004 10:14:12 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.1) Gecko/20040801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Oppermann References: <1092881027.999.3.camel@server.mcneil.com> <412497B5.6040203@freebsd.org> In-Reply-To: <412497B5.6040203@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: Sean McNeil Subject: Re: ipfw2 broken 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: Thu, 19 Aug 2004 16:16:51 -0000 Andre Oppermann wrote: > Sean McNeil wrote: > >> How do I get the ipfw2 module to compile with divert? It doesn't >> recognize the following in my config file when building the module: >> >> options IPFIREWALL_FORWARD >> options IPDIVERT >> >> Also, the /etc/rc.d/ipfw script is looking for an invalid sysctl var: >> >> net.inet.ip.fw.enable >> >> and it will fail if I have the IPFIREWALL option which compiles the code >> into the kernel because it will try to load and return 1 on a failure. > > > I'm looking into it and will have a fix later today. > This, and all of the rc.d, module loading, and kernel option problems are now a blocking issue for BETA1. We had planned to start the BETA1 no later than 2200 UTC today. What is your schedule for getting all of this fixed? Scott