From owner-freebsd-current@FreeBSD.ORG Wed Jul 23 20:40:52 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E269F9EC for ; Wed, 23 Jul 2014 20:40:52 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id BA6152810 for ; Wed, 23 Jul 2014 20:40:52 +0000 (UTC) Received: from [192.168.1.2] (senat1-01.HML3.ScaleEngine.net [209.51.186.5]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id C02E22AB17 for ; Wed, 23 Jul 2014 20:40:44 +0000 (UTC) Message-ID: <53D01DDD.8000806@freebsd.org> Date: Wed, 23 Jul 2014 16:41:01 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Future of pf / firewall in FreeBSD ? - does it have one ? References: <201407231542.s6NFgX4M025370@slippy.cwsent.com> <50E4E363-B2C0-4ED7-A0C4-2D7C69FF15B2@lists.zabbadoz.net> In-Reply-To: <50E4E363-B2C0-4ED7-A0C4-2D7C69FF15B2@lists.zabbadoz.net> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cJwmkE94vk3BjoX0RuEFnQx8sfem5efNC" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Wed, 23 Jul 2014 20:40:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --cJwmkE94vk3BjoX0RuEFnQx8sfem5efNC Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2014-07-23 16:38, Bjoern A. Zeeb wrote: > On 23 Jul 2014, at 15:42 , Cy Schubert wrote= : >=20 >> Taking this discussion slightly sideways but touching on this thread a= =20 >> little, each of our packet filters will need nat66 support too. Pf doe= sn't=20 >> support it for sure. I've been told that ipfw may and I suspect ipfilt= er=20 >> doesn't as it was on Darren's todo list from 2009. >=20 > our pf does support IPv6 prefix rewriting quite nicely and has for year= s. >=20 > =97=20 > Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 198= 3 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 Bjoern: What IPv6 stuff does our pf not do well? --=20 Allan Jude --cJwmkE94vk3BjoX0RuEFnQx8sfem5efNC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJT0B3gAAoJEJrBFpNRJZKfRZsP/3TS7cJ4HgMXqR+RckBImoFr uu9j8nR9dgAbptM3/H5GaHa7qdLZvBF+RfKH/zetplp/LHsSlPKgvFOc4RMZut6v Q7TrO2INNMQfEJexRXBFS9z3m1EvHYAqvr3WakaaOLNg9lmpQ3yTYght6BF9tP6V N8JxWmw1FTQ3MkfrxSf4NtkTC9pystSt3BqEdKa9qdpw1ZOE0eoiEfOgN85tZ0gn JcrBX5F0D8lCDVF7tGu/ZMwXTp1eTj0wl/WZwM3fXNWYBsOeiz1xFDiodpkiQ41A LYmX0Gr6kCkRTjUXiUmQYElMHzXZtgW8nHL4kjJLkSaoXNMkAqJTIFQbjdzigC1I 3uSgYLKmKlpuw/9KaH15r4DnzR0nu08DreQvHmNGT1J3uHHKuC3ab9wKUm46yqhl RmdJ1EJ+U2T8QZchOc/ZH9tctUgqxkTq7ttjtBwi3Ovi/55iJwAIulP9cPXqFN1h 2zX0NZLEawRMfT1B1nJmtBfm2m+XpNYmF6Rybq4XguMhZS4f9SdK6lmdgJDt6Zff pgASs1nDAvqduAo24t6Ki/0g9r0dVorlFsRnikXQ9YJxinHYdCtjoGSxNQeI8qYo mHaB1MCrlKeTFRerEuDhwFmQHvutNb7vtAbBVbFGaX62cevGv4wu50PW9DSFWk3H AUGjREbujluuH0s0i6R3 =qyXD -----END PGP SIGNATURE----- --cJwmkE94vk3BjoX0RuEFnQx8sfem5efNC--