From owner-freebsd-current@FreeBSD.ORG Thu Aug 19 17:22:37 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 70EDE16A4D9 for ; Thu, 19 Aug 2004 17:22:37 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A768A43D41 for ; Thu, 19 Aug 2004 17:22:36 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 15781 invoked from network); 19 Aug 2004 17:22:17 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 19 Aug 2004 17:22:17 -0000 Message-ID: <4124E1DA.B5341C04@freebsd.org> Date: Thu, 19 Aug 2004 19:22:34 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin References: <1092881027.999.3.camel@server.mcneil.com> <412497B5.6040203@freebsd.org> <4124D1D4.5080307@samsco.org> <200408191251.32319.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 17:22:37 -0000 John Baldwin wrote: > > On Thursday 19 August 2004 12:14 pm, Scott Long wrote: > > 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? > > It looks like fixing the rc.d script is simply a matter of checking for the fw > node rather than fw.enable. The pfil(9) requirement is just a matter of > documenting the new requirement. The IPDIVERT thing is probably larger > though. :( We may need to just tell people to compile ipfw into the kernel > for now if they want divert sockets, much as they do if they want 'default to > accept'. IPDIVERT wasn't compiled into the module before. It's surrounded by #if !defined(KLD_MODULE). However if the kernel was compiled with option IPDIVERT but w/o IPFIREWALL is was working anyway. -- Andre