Date: Mon, 25 Oct 2004 13:42:44 -0700 From: Sean McNeil <sean@mcneil.com> To: Andre Oppermann <andre@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: make buildkernel failed related to ip_divert module Message-ID: <1098736963.44975.3.camel@server.mcneil.com> In-Reply-To: <417D6148.6050807@freebsd.org> References: <417B128B.7080904@gddsn.org.cn> <417D5E51.2060100@freebsd.org><417D6148.6050807@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-ww18xAL64SjS9RbETnBP Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2004-10-25 at 13:25, Andre Oppermann wrote: > Sean McNeil wrote: > > On Mon, 2004-10-25 at 13:13, Andre Oppermann wrote: > >>Conrad J. Sabatier wrote: > >>>For a further bit of clarification (I know, should have done this the > >>>first time): > >>> > >>>This problem is occurring with the following kernel options: > >>> > >>>options IPDIVERT > >>>options IPFILTER > >>>options IPFILTER_LOG > >>> > >>>The only workaround at this time is adding "options IPFIREWALL". > >> > >>Yes, that is correct. > >> > >>IPDIVERT is a module now and you can dynamically load it just like you > >>can load ipfw (options IPFIREWALL). > >> > >>IPDIVERT depends on ipfw being loaded or compiled into the kernel. > >> > >>I have done the last step of IPDIVERT's transition into a KLD a few > >>minutes ago. It will warn you now if you try to compile it into a > >>kernel without IPFIREWALL as well. As a module it will simply complain > >>that ipfw needs to be loaded first. > >=20 > >=20 > > I build my kernel with > >=20 > > options IPFIREWALL > > options IPFIREWALL_FORWARD > > options IPDIVERT > >=20 > > Can I now use loadable modules as well? Will IPFIREWALL have the > > forwarding option or would I still have to specify that? >=20 > You can certainly use IPDIVERT as a loadable module. The FORWARD option > to IPFIREWALL needs to be compiled into the module if you want to load > it as a module. For modules options in the kernel configuration file > are not automatically included. You have to edit sys/modules/ipfw/Makefi= le > instead. Then you can load everything as module. If you start natd from > rc.conf it will load ipdivert.ko automatically (if you have run mergemast= er > to update your rc scripts). OK, thanks. I thought someone was working on module configuration from the kernel configuration file instead of having to hack the Makefile for each module. That is a pita. Cheers, Sean --=-ww18xAL64SjS9RbETnBP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBfWVDyQsGN30uGE4RAsUjAJkBveL/vSUpFlsM2yJwMgchhIpNQwCg2kH9 aUSQKw0Dg90DzESF/kOuDKI= =M4iy -----END PGP SIGNATURE----- --=-ww18xAL64SjS9RbETnBP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1098736963.44975.3.camel>