Re: make buildkernel failed related to ip_divert module

On Mon, 2004-10-25 at 13:13, Andre Oppermann wrote:
> Conrad J. Sabatier wrote:
> > On Sun, 24 Oct 2004 13:30:45 -0500, "Conrad J. Sabatier"
> > <conrads_at_cox.net> wrote:
> > 
> > 
> >>On Sun, 24 Oct 2004 10:25:15 +0800, wsk <wsk_at_gddsn.org.cn> wrote:
> >>
> >>
> >>>rm -f hack.c
> >>>MAKE=/usr/obj/usr/src/make.i386/make sh /usr/src/sys/conf/newvers.sh
> >>>WSK cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
> >>>-Wstrict-prototypes -W missing-prototypes -Wpointer-arith -Winline
> >>>-Wcast-qual -fformat-extensions -st d=c99 -nostdinc -I- -I.
> >>>-I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/us
> >>>r/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
> >>>-I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath
> >>>-I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/sr c/sys/contrib/ngatm
> >>>-D_KERNEL -include opt_global.h -fno-common -finline-limit=8 000
> >>>--param inline-unit-growth=100 --param large-function-growth=1000
> >>>-mno-alig n-long-strings -mpreferred-stack-boundary=2 -ffreestanding
> >>>-Werror vers.c linking kernel
> >>>ip_divert.o(.text+0x1238): In function `div_modevent':
> >>>: undefined reference to `ip_divert_ptr'
> >>>ip_divert.o(.text+0x12c2): In function `div_modevent':
> >>>: undefined reference to `ip_divert_ptr'
> >>>*** Error code 1
> >>>
> >>>Stop in /usr/obj/usr/src/sys/WSK.
> >>>*** Error code 1
> >>
> >>Same deal with amd64.
> > 
> > 
> > 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.

I build my kernel with

options         IPFIREWALL
options         IPFIREWALL_FORWARD
options         IPDIVERT

Can I now use loadable modules as well?  Will IPFIREWALL have the
forwarding option or would I still have to specify that?

I prefer a minimalist approach to my config and to load modules instead.

Cheers,
Sean