From owner-freebsd-stable@FreeBSD.ORG Tue Apr 15 06:27:34 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7174C37B401 for ; Tue, 15 Apr 2003 06:27:34 -0700 (PDT) Received: from pa-plum1b-166.pit.adelphia.net (pa-plum1b-122.pit.adelphia.net [24.53.161.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id B487F43F75 for ; Tue, 15 Apr 2003 06:27:33 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (working [172.16.0.95]) h3FDRWJP017409; Tue, 15 Apr 2003 09:27:32 -0400 (EDT) (envelope-from wmoran@potentialtech.com) Message-ID: <3E9C08C4.5040702@potentialtech.com> Date: Tue, 15 Apr 2003 09:27:32 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030301 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vizion communication References: <00e101c302fb$5f8b5700$15b55042@vizion2000.net> In-Reply-To: <00e101c302fb$5f8b5700$15b55042@vizion2000.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Stable Subject: Re: NAT proxy concepts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2003 13:27:34 -0000 vizion communication wrote: > I have been taking a close look at some networking > opportunities which are being frustrated by the limits which > are imposed by NAT. In particular the constraints impose by > the embargo on double NATing have an impact for a project I > am working on. Has anyone ever seen anything which I would > conceptually describe as a reverse NAT proxy? See the -redirect_port option in the man page for natd ... is that what you're referring to? > What I want to be able to do is to be able to create a > heirarchical tier of networks each one of which > communicates to the network above by using a modification of > NAT enjoying the capability of identifying a subnet number > and client. If you're using a "cascading gateway" layout, then nat isn't really required ... except on the gateway that actually connects to the Internet. This is a fairly common configuration. > Does ayone know enough about this subject to point me in the > right > direction (which may be - forget about it there is no way it > can be done..:-) Don't see any reason why it can't be done ... if I'm understanding your correctly. -- Bill Moran Potential Technologies http://www.potentialtech.com