From mboxrd@z Thu Jan  1 00:00:00 1970
From: Taylor Grant <gtaylor@riverviewtech.net>
Subject: Re: can you specify incoming *AND* outgoing NIC on a FORWARD rule?
Date: Wed, 13 Apr 2005 19:27:24 -0500
Message-ID: <425DB8EC.9040907@riverviewtech.net>
References: <1113425048.3544.169.camel@seberino.spawar.navy.mil>
	<20050413205556.GA31258@bender.817west.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <netfilter-bounces@lists.netfilter.org>
In-Reply-To: <20050413205556.GA31258@bender.817west.com>
List-Id: <netfilter.vger.kernel.org>
List-Unsubscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>,
	<mailto:netfilter-request@lists.netfilter.org?subject=unsubscribe>
List-Archive: </pipermail/netfilter>
List-Post: <mailto:netfilter@lists.netfilter.org>
List-Help: <mailto:netfilter-request@lists.netfilter.org?subject=help>
List-Subscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>,
	<mailto:netfilter-request@lists.netfilter.org?subject=subscribe>
Sender: netfilter-bounces@lists.netfilter.org
Errors-To: netfilter-bounces@lists.netfilter.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: Jason Opperisano <opie@817west.com>
Cc: netfilter@lists.netfilter.org

> precisely.

You beat me to the punch.  That is exactly what FORWARD does in allowing you to specify an inbound (-i) and outbound (-o) interface.



Grant. . . .