Date: Sun, 04 Nov 2001 19:16:24 -0600 From: David Kelly <dkelly@hiwaay.net> To: "Jason Cribbins" <jasonc@concentric.net> Cc: "Nick Rogness" <nick@rogness.net>, questions@FreeBSD.ORG Subject: Re: Unable to get natd/ipfw to work properly Message-ID: <200111050116.fA51GPo68305@grumpy.dyndns.org> In-Reply-To: Message from "Jason Cribbins" <jasonc@concentric.net> of "Sun, 04 Nov 2001 15:13:34 EST." <001701c1656d$2f97c240$05d85c42@kibserv.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Jason Cribbins" writes: > I rebuilt the kernel using the directions found on > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html > using the "traditional" method since the "new" method wouldn't work > correctly. > I have confirmed the new kernel ident is displayed upon bootup. > > Now I am back top this again > IP packet filtering initialized, divert disabled, rule-based forwarding > disabled > , default to deny, logging disabled > > and this as well. > 7:58pm mail:~ # ipfw add divert natd all from any to any via lnc0 > ipfw: getsockopt(IP_FW_ADD): Invalid argument > 7:58pm mail:~ # > > What am I missing here? On reboot if you had firewall_enable="yes" in /etc/rc.conf then it would have run "kldload ipfw" for you. Short of reboot you could do it yourself on the command line. Read /etc/rc.network to see what happens. Can't say for sure if IPDIVERT would be included in the ipfw kld but am guessing it would. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111050116.fA51GPo68305>