From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 17 12:20:34 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2306D16A4CE for ; Wed, 17 Nov 2004 12:20:34 +0000 (GMT) Received: from grsu.by (grsu.by [194.158.202.115]) by mx1.FreeBSD.org (Postfix) with SMTP id A76AE43D2F for ; Wed, 17 Nov 2004 12:20:30 +0000 (GMT) (envelope-from grog@grsu.by) Received: (qmail 63003 invoked from network); 17 Nov 2004 12:19:18 -0000 Received: from unknown (HELO ?10.31.16.99?) (grog@10.31.16.99) by grsu.by with SMTP; 17 Nov 2004 12:19:17 -0000 Message-ID: <419B443F.8010708@grsu.by> Date: Wed, 17 Nov 2004 14:29:51 +0200 From: Yury Tarasievich User-Agent: Mozilla Thunderbird 0.9 (X11/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitry Morozovsky 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> In-Reply-To: <20041117003432.P71104@woozle.rinet.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: IPDIVERT option not getting compiled? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 12:20:34 -0000 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