Date: Thu, 19 Aug 2004 12:51:32 -0400 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: Sean McNeil <sean@mcneil.com> Subject: Re: ipfw2 broken Message-ID: <200408191251.32319.jhb@FreeBSD.org> In-Reply-To: <4124D1D4.5080307@samsco.org> References: <1092881027.999.3.camel@server.mcneil.com> <412497B5.6040203@freebsd.org> <4124D1D4.5080307@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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'. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408191251.32319.jhb>