From owner-freebsd-questions  Wed Feb 12 07:13:25 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA03155
          for questions-outgoing; Wed, 12 Feb 1997 07:13:25 -0800 (PST)
Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA03142
          for <questions@FreeBSD.ORG>; Wed, 12 Feb 1997 07:12:30 -0800 (PST)
Received: (from tinguely@localhost) by plains.nodak.edu (8.8.4/8.8.3) id JAA27218; Wed, 12 Feb 1997 09:11:19 -0600 (CST)
Date: Wed, 12 Feb 1997 09:11:19 -0600 (CST)
From: Mark Tinguely <tinguely@plains.nodak.edu>
Message-Id: <199702121511.JAA27218@plains.nodak.edu>
To: mfwong@mol.net.my, questions@FreeBSD.ORG
Subject: Re: NAT implementation ?
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>  I realize that there is NAT for PPP now, but what about other type
>  of interface ? Is NAT meant to be interface device independent or
>  dependent ? I bought an ET 64K sync card but the driver doesn't have
>  NAT and I am hoping to see FreeBSD may have kernel NAT support in
>  future or now ? 8-)))

There is two ways to do Network Address Translation. The first you mentioned
is built into the user PPP code (http://www.srv.net/~cmott/alias.html).

The second is built into the IP Filter code (http://coombs.anu.edu.au/~avalon/)
With this second way you can use any IP interface for the translation.
The IP Filter NAT method requires some additional proxies (such as a
ftp proxy).

--mark.