From owner-freebsd-questions Mon Jun 21 11: 9: 9 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 16F2715162 for ; Mon, 21 Jun 1999 11:09:04 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id LAA61665; Mon, 21 Jun 1999 11:09:02 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 21 Jun 1999 11:09:02 -0700 (PDT) From: Doug White To: myers@iname.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 'ipfw fwd' question: Shouldn't this work? In-Reply-To: <199906200546.WAA07308@sol.> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Jun 1999 myers@iname.com wrote: > > > This sounds like a job for natd more than ipfw fwd. Are you running fake > > IPs inside your network? > > > natd didn't work either, though I'm perfectly willing to accept that I > may have set it up wrong. Fake IPs? Let's call them unregistered. > 10.0.0.1 is the web server I want to forward packets to. 10.0.0.254 is > the gateway, which maintains a legal IP address on its outward-looking > interface. > > The natd syntax goes something like 'natd -redirect_port "tcp > 10.0.0.1:80 80"', I believe... That's not all of it, but you have the redirect_port option right. You need the -n option to natd to specify the (exterior) interface to translate on. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message