From owner-freebsd-current@FreeBSD.ORG  Thu Jul 31 12:20:42 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 9A75AB5F
 for <freebsd-current@freebsd.org>; Thu, 31 Jul 2014 12:20:42 +0000 (UTC)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6AE9B247B
 for <freebsd-current@freebsd.org>; Thu, 31 Jul 2014 12:20:41 +0000 (UTC)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by gateway1.nyi.internal (Postfix) with ESMTP id 1FE1D2114F
 for <freebsd-current@freebsd.org>; Thu, 31 Jul 2014 08:20:30 -0400 (EDT)
Received: from frontend1 ([10.202.2.160])
 by compute4.internal (MEProxy); Thu, 31 Jul 2014 08:20:30 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:date:from:mime-version:to
 :subject:references:in-reply-to:content-type
 :content-transfer-encoding; s=smtpout; bh=jI7/psPp7RgNiKed66890B
 tj7So=; b=oxF8p+C+iAiN0xarkPol5e+CHBo/a1YZEGgf1YI4Y8/pVtyC2abzwL
 UsftR32AT5pYucXLGbbHTUWOZgPYrzzqvTdWxTgc67bNlAy+HOFm8eiWGT7UNWph
 mhUPGlc45wstf3wF3qI49ggx0Ud992BtnRBtiCcJ84sqx1DW0jAz8=
X-Sasl-enc: 6DUKxZxMGpJzXwThFLDnM6rKfZJ1Lzro11KiWEsnPB+8 1406809229
Received: from [192.168.1.31] (unknown [203.206.138.26])
 by mail.messagingengine.com (Postfix) with ESMTPA id 403CFC00005
 for <freebsd-current@freebsd.org>; Thu, 31 Jul 2014 08:20:29 -0400 (EDT)
Message-ID: <53DA3488.2050801@freebsd.org>
Date: Thu, 31 Jul 2014 22:20:24 +1000
From: Darren Reed <darrenr@freebsd.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Subject: Re: Future of pf / firewall in FreeBSD ? - does it have one ?
References: <201407291320.s6TDK5ZS005328@slippy.cwsent.com>
 <444fc5248aaa7d474cf9bde66f3d7f64@mailbox.ijs.si>
 <CAN6yY1uqCghJ1in5-Z8Ww6VOALuuqH3R9wFw=wEr5dd3iFbYOw@mail.gmail.com>
In-Reply-To: <CAN6yY1uqCghJ1in5-Z8Ww6VOALuuqH3R9wFw=wEr5dd3iFbYOw@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2014 12:20:42 -0000

On 30/07/2014 2:54 AM, Kevin Oberman wrote:
> ...
> I would hope that is not the case. While NAT66 is "well known" and has been
> a topic of discussion for years, NPT66 is relatively new. It does share
> many concepts with NAT66 (and, most likely implementations also share
> code), but does not require any state, making it vastly less complex and no
> longer breaks point to point networking. The names look similar, which may
> result in unfortunate confusion, but NPT66 may be the bast solution to a
> real problem and it does not create the issues of NAT66.

NPT66 is a subset of NAT66.

Cheers,
Darren