From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 16 21:35:55 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 C235816A4CE for ; Tue, 16 Nov 2004 21:35:55 +0000 (GMT) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0290B43D2D for ; Tue, 16 Nov 2004 21:35:55 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.1/8.13.1) with ESMTP id iAGLZqkY071458; Wed, 17 Nov 2004 00:35:52 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Wed, 17 Nov 2004 00:35:52 +0300 (MSK) From: Dmitry Morozovsky To: Yury Tarasievich In-Reply-To: <20041117003227.G71104@woozle.rinet.ru> Message-ID: <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> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Yar Tikhiy 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: Tue, 16 Nov 2004 21:35:55 -0000 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 *** ------------------------------------------------------------------------