From owner-freebsd-ipfw@FreeBSD.ORG  Tue Feb  3 10:04:23 2015
Return-Path: <owner-freebsd-ipfw@FreeBSD.ORG>
Delivered-To: freebsd-ipfw@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id AAC4EDC3;
 Tue,  3 Feb 2015 10:04:23 +0000 (UTC)
Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 07C2DFA;
 Tue,  3 Feb 2015 10:04:22 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id t13A4Fcb073244;
 Tue, 3 Feb 2015 21:04:16 +1100 (EST)
 (envelope-from smithi@nimnet.asn.au)
Date: Tue, 3 Feb 2015 21:04:15 +1100 (EST)
From: Ian Smith <smithi@nimnet.asn.au>
To: Lev Serebryakov <lev@freebsd.org>
Subject: Re: [RFC][patch] Two new actions: state-allow and state-deny
In-Reply-To: <54CFCD45.9070304@FreeBSD.org>
Message-ID: <20150203205715.A38620@sola.nimnet.asn.au>
References: <54CFCD45.9070304@FreeBSD.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <20150203205715.E38620@sola.nimnet.asn.au>
Cc: freebsd-ipfw <freebsd-ipfw@freebsd.org>,
 freebsd-net <freebsd-net@freebsd.org>
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw/>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 10:04:23 -0000

On Mon, 2 Feb 2015 22:17:25 +0300, Lev Serebryakov wrote:

 >  Now to make stateful firewall with NAT you need to make some not very
 > "readable" tricks to record state ("allow") of outbound connection
 > before NAT, but pass packet to NAT after that. I know two:
 > 
 >  (a) skipto-nat-allow pattern from many HOWOTOs

Lev, can you provide references for these HOWTOs you refer to?

I have a suspicion that some of them should be taken out and shot.

cheers, Ian