Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Nov 2004 14:29:51 +0200
From:      Yury Tarasievich <grog@grsu.by>
To:        Dmitry Morozovsky <marck@rinet.ru>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: IPDIVERT option not getting compiled?
Message-ID:  <419B443F.8010708@grsu.by>
In-Reply-To: <20041117003432.P71104@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> <20041117003432.P71104@woozle.rinet.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Dmitry Morozovsky wrote:

> 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?

Not anymore. I've finally went for reformatting and reinstalling. Then 
it all worked -- and with this same config file.

And I'm reasonably sure I wasn't messing with system in previous 
installation.

What I'd like to know now is what could be the possible cause??

--regards



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?419B443F.8010708>