Date: Thu, 5 Apr 2007 16:01:01 +0200 From: Jonathan McKeown <jonathan@hst.org.za> To: freebsd-questions@freebsd.org Cc: Terry Todd <tlt@badger.tltodd.com> Subject: Re: ipfw fwd not working in 6.2-release Message-ID: <200704051601.01747.jonathan@hst.org.za> In-Reply-To: <20070405084208.A4130@badger.tltodd.com> References: <20070403105841.A98763@badger.tltodd.com> <20070405084208.A4130@badger.tltodd.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Thursday 05 April 2007 15:42, Terry Todd wrote: > > On Tue, Apr 03, 2007 at 10:58:41AM -0500, Terry Todd wrote: > > I have tried to get ipfw fwd to work in 6.2-release but it always barfs. > > > > I have recompiled and installed a custom kernel with > > options IPFIREWALL_FORWARD [adding a fwd rule] > > ipfw: getsockopt(IP_FW_ADD): Invalid argument [snip] > > Anyone else see this behaviour? > I tried this on a second machine and it does the same thing. > > ipfw: getsockopt(IP_FW_ADD): Invalid argument > > Could someone try running this on a 6.2-RELEASE system and tell me what you > get: > > # ipfw add forward 127.0.0.1,3128 tcp from not me to any 80 in via > [interface device] I'm seeing the same thing having just upgraded a working 6.0-RELEASE box. Since the only kernel option I had set on either version of the OS was IPFIREWALL_FORWARD, the system is loading ipfw.ko, ipdivert.ko and dummynet.ko automatically. Has the way ipfw.ko is built changed? Do we need to compile ipfw into the kernel to use ipfw fwd rules now? Or can I force ipfw.ko to be rebuilt with forwarding included? Jonathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704051601.01747.jonathan>