From owner-freebsd-stable@FreeBSD.ORG Sun Feb 19 04:34:39 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 793FD16A422; Sun, 19 Feb 2006 04:34:39 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 794D543D49; Sun, 19 Feb 2006 04:34:38 +0000 (GMT) (envelope-from max@love2party.net) Received: from [84.163.245.121] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis), id 0ML21M-1FAgHD0kGj-0006uY; Sun, 19 Feb 2006 05:34:27 +0100 From: Max Laier Organization: FreeBSD To: freebsd-stable@freebsd.org Date: Sun, 19 Feb 2006 05:34:23 +0100 User-Agent: KMail/1.9.1 References: <5e9d9fe557ea6dedf8f173c257a0c7a9@kobudo.homeunix.net> <43F7CB2B.30402@plosh.net> In-Reply-To: <43F7CB2B.30402@plosh.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5862052.czS5LRG0pz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200602190534.37261.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Peter Losher 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 04:34:39 -0000 --nextPart5862052.czS5LRG0pz Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 19 February 2006 02:34, Peter Losher wrote: > 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. > > Will this change in 6.1, or will we have to wait for ip6fw to be > completly removed before the module will support v6 by default? (You > would have to admit that it's somewhat confusing the way it is now) IPFW[2] has gained some IPv6 functionality lately and was supposed to repla= ce=20 IP6FW in the long run. It turned out, however, that IPFW[2] is not a=20 complete in-place replacement for IP6FW as IPFW2 syntax has diverted from t= he=20 IPFW1/IP6FW syntax too much. I am unsure about the plans for IPFW+IPv6 in= =20 RELENG_6, HEAD certainly moves to removal of IP6FW, but more testers as=20 required. Any datapoints with HEAD's version of IPFW+IPv6 are much appreciated. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart5862052.czS5LRG0pz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBD9/VdXyyEoT62BG0RAiFqAJ9zNSribSa1eK+RmvfvRlkxS9JONwCfUuRH XlV/N03Eqb6WZQZSrwYrOHE= =YX1w -----END PGP SIGNATURE----- --nextPart5862052.czS5LRG0pz--