Date: Sun, 4 Nov 2001 23:17:46 -0800 From: "Crist J. Clark" <cristjc@earthlink.net> To: David Kelly <dkelly@hiwaay.net> Cc: Nick Rogness <nick@rogness.net>, Jason Cribbins <jasonc@concentric.net>, questions@FreeBSD.ORG Subject: Re: Unable to get natd/ipfw to work properly Message-ID: <20011104231746.D325@blossom.cjclark.org> In-Reply-To: <200111050219.fA52JWo68761@grumpy.dyndns.org>; from dkelly@hiwaay.net on Sun, Nov 04, 2001 at 08:19:32PM -0600 References: <nick@rogness.net> <200111050219.fA52JWo68761@grumpy.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 04, 2001 at 08:19:32PM -0600, David Kelly wrote:
> Nick Rogness writes:
> > On Sun, 4 Nov 2001, David Kelly wrote:
> >
> > > "Jason Cribbins" writes:
> > [SNIP]
> > >
> > > Can't say for sure if IPDIVERT would be included in the ipfw kld but
> > > am guessing it would.
> > >
> >
> > You must build IPDIVERT into the kernel
> > manually as there is no klm for DIVERT and it is not part of
> > ipfw.ko. Or at least it wasn't before 4.4-R.
>
> OK, then that would be a nice simple little thing for somebody to
> contribute to /etc/rc.network. The script knows if it has to kldload
> ipfw, and if it loaded from kld then is there any chance IPDIVERT will
> work? If not, then a verbose warning would be nice if such were
> attempted.
There is nothing stopping someone from adding IPDIVERT to their
ipfw.ko module. Edit src/sys/modules/ipfw/Makefile.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
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?20011104231746.D325>