From owner-freebsd-ipfw@FreeBSD.ORG  Mon Jul  9 23:42:49 2012
Return-Path: <owner-freebsd-ipfw@FreeBSD.ORG>
Delivered-To: freebsd-ipfw@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 715C61065675
	for <freebsd-ipfw@freebsd.org>; Mon,  9 Jul 2012 23:42:49 +0000 (UTC)
	(envelope-from rg@progtech.net)
Received: from webfw.progtech.net (fw1.progtech.net [195.226.167.243])
	by mx1.freebsd.org (Postfix) with ESMTP id E5CFA8FC0C
	for <freebsd-ipfw@freebsd.org>; Mon,  9 Jul 2012 23:42:48 +0000 (UTC)
X-Virus-Scanned: amavisd-new at progtech.net
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by webfw.progtech.net (8.14.5/8.14.2) with ESMTP id q69NI4Nx041301
	for <freebsd-ipfw@freebsd.org>; Tue, 10 Jul 2012 01:18:04 +0200 (CEST)
	(envelope-from rg@progtech.net)
Message-ID: <4FFB66AB.2020306@progtech.net>
Date: Tue, 10 Jul 2012 01:18:03 +0200
From: Rolf Grossmann <rg@progtech.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: freebsd-ipfw@freebsd.org
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Equivalent of in_port and out_port with in-kernel nat?
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Mon, 09 Jul 2012 23:42:49 -0000

Hi,

I've started switching my machines to in-kernel nat and I've run into a
case where I need to tell the nat instance which packets to treat as
incoming and which as outgoing. With natd I've been able to use divert
with different ports and in_port and out_port options. The in-kernel nat
however doesn't seem to have a method of specifying nat direction and
instead always uses the information from the interface.

My question is, am I missing something? Is there a patch I could try?
Has the issue even come up before?

Thanks, Rolf.