From owner-freebsd-current@FreeBSD.ORG Tue Oct 26 12:29:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81F4116A4CE for ; Tue, 26 Oct 2004 12:29:47 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A69E043D49 for ; Tue, 26 Oct 2004 12:29:46 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 19649 invoked from network); 26 Oct 2004 12:27:30 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 26 Oct 2004 12:27:30 -0000 Message-ID: <417E4337.80804@freebsd.org> Date: Tue, 26 Oct 2004 14:29:43 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a1) Gecko/20040520 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Conrad J. Sabatier" References: <417B128B.7080904@gddsn.org.cn> <20041024133045.40733f45@dolphin.local.net> <20041024144743.37fb5c69@dolphin.local.net> <417D5E51.2060100@freebsd.org> <20041025214401.31d63ee4@dolphin.local.net> In-Reply-To: <20041025214401.31d63ee4@dolphin.local.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: make buildkernel failed related to ip_divert module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 12:29:47 -0000 Conrad J. Sabatier wrote: > On Mon, 25 Oct 2004 22:13:05 +0200, Andre Oppermann > wrote: > > >>Conrad J. Sabatier wrote: >> >>>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. > > Hmmm. I'm confused now. Up until a day or two ago, the kernel would > compile just fine without IPFIREWALL. When did IPDIVERT come to depend > on IPFIREWALL, and why? > > Or maybe I'm just *really* confused. I thought I needed IPDIVERT for > ipnat to work, or am I mistaken? Yes, you are confused. ;) IPDIVERT is only required for NAT with ipfw (a.k.a. IPFIREWALL). > What exactly do I need now to use ipf and ipnat? ipf and ipnat. Nothing else in the kernel. -- Andre