From owner-freebsd-current@FreeBSD.ORG Wed Jul 23 20:39:27 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 F374E8C8 for ; Wed, 23 Jul 2014 20:39:26 +0000 (UTC) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AB45627FC for ; Wed, 23 Jul 2014 20:39:26 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 7E95B25D3897; Wed, 23 Jul 2014 20:39:23 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 3FF9BC24020; Wed, 23 Jul 2014 20:39:22 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 6SP563jOq0T3; Wed, 23 Jul 2014 20:39:20 +0000 (UTC) Received: from [IPv6:fde9:577b:c1a9:4410:84e6:ae89:68a6:d418] (unknown [IPv6:fde9:577b:c1a9:4410:84e6:ae89:68a6:d418]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 7B46ABFDDA0; Wed, 23 Jul 2014 20:39:18 +0000 (UTC) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Future of pf / firewall in FreeBSD ? - does it have one ? From: "Bjoern A. Zeeb" In-Reply-To: <201407231542.s6NFgX4M025370@slippy.cwsent.com> Date: Wed, 23 Jul 2014 20:38:58 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <50E4E363-B2C0-4ED7-A0C4-2D7C69FF15B2@lists.zabbadoz.net> References: <201407231542.s6NFgX4M025370@slippy.cwsent.com> To: Cy Schubert X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-current@freebsd.org 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:39:27 -0000 On 23 Jul 2014, at 15:42 , Cy Schubert wrote: > Taking this discussion slightly sideways but touching on this thread a=20= > little, each of our packet filters will need nat66 support too. Pf = doesn't=20 > support it for sure. I've been told that ipfw may and I suspect = ipfilter=20 > doesn't as it was on Darren's todo list from 2009. our pf does support IPv6 prefix rewriting quite nicely and has for = years. =97=20 Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 1983