From owner-freebsd-stable@FreeBSD.ORG Sun Feb 19 11:15:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68B7416A420; Sun, 19 Feb 2006 11:15:36 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7641243D46; Sun, 19 Feb 2006 11:15:32 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id k1JBFL4Z022871; Sun, 19 Feb 2006 14:15:21 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id k1JBFLtL022870; Sun, 19 Feb 2006 14:15:21 +0300 (MSK) (envelope-from yar) Date: Sun, 19 Feb 2006 14:15:20 +0300 From: Yar Tikhiy To: Hajimu UMEMOTO Message-ID: <20060219111520.GD20500@comp.chem.msu.su> References: <5e9d9fe557ea6dedf8f173c257a0c7a9@kobudo.homeunix.net> <43F7CB2B.30402@plosh.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Cc: Peter Losher , freebsd-stable@freebsd.org Subject: Re: IPv6 and IPFW X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2006 11:15:36 -0000 On Sun, Feb 19, 2006 at 04:38:21PM +0900, Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Sat, 18 Feb 2006 17:34:35 -0800 > >>>>> Peter Losher said: > > plosher> [1 ] > plosher> Hajimu UMEMOTO wrote: > > > The ipfw in 6-STABLE has an IPv6 awareness, but it is not enabled as > > far as you use ipfw as a KLD module. If ipfw is compiled into kernel, > > ipfw does filterling an IPv6 as well. > > plosher> Will this change in 6.1, or will we have to wait for ip6fw to be > plosher> completly removed before the module will support v6 by default? (You > plosher> would have to admit that it's somewhat confusing the way it is now) > > It was already MFC'ed into RELENG_6. So, ipfw.ko obeys the kernel > config, now. Please note here that ipfw.ko obeys INET6 and IPSEC options, but not IPFIREWALL_* ones yet. The latter still are to be fixed for the module build. -- Yar