Date: Wed, 17 Nov 2004 00:35:52 +0300 (MSK) From: Dmitry Morozovsky <marck@rinet.ru> To: Yury Tarasievich <grog@grsu.by> Cc: freebsd-hackers@freebsd.org Subject: Re: IPDIVERT option not getting compiled? Message-ID: <20041117003432.P71104@woozle.rinet.ru> In-Reply-To: <20041117003227.G71104@woozle.rinet.ru> References: <200411151836.iAFIa6b2007989@peedub.jennejohn.org> <4199FBE6.60200@grsu.by> <20041116151643.GA74432@comp.chem.msu.su> <419A1FB9.108@grsu.by> <20041117003227.G71104@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Nov 2004, Dmitry Morozovsky wrote:
DM> YT> > > I'm adding IPDIVERT option ("options IPDIVERT") to config file and
DM> YT> <...>
DM> YT> > You seem to be confused by the well-known kernel vs. module
DM> YT> > configuration issue. Alas, kernel options you specify in your
DM> YT> > kernel config file affect the kernel binary only, not modules
DM> YT> > built along with the kernel. If you want IPDIVERT, which is
DM> YT> > an option to IPFIREWALL, you have to build your kernel with
DM> YT> > both IPFIREWALL and IPDIVERT:
DM> YT> <...>
DM> YT> I did. See the config contents in originating posting. That was the essence
DM> YT> of the problem -- familiar procedure unexplainably not working.
DM>
DM> But you did reference ipfw *module*. This combination will not work. Currently,
DM> if you need divert you *must* compile ipfw into 4.X kernel.
Hmm. Looking at you kernel config file I see you *did* included ipfw into the
kernel. Looks strange to me.
Well, can you please provide dmesg from the failing boot?
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041117003432.P71104>