From owner-freebsd-net@FreeBSD.ORG Tue Jan 25 23:14:00 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0482016A4CF for ; Tue, 25 Jan 2005 23:14:00 +0000 (GMT) Received: from thor-new.fsklaw.com (adsl-64-174-116-34.dsl.lsan03.pacbell.net [64.174.116.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B47243D4C for ; Tue, 25 Jan 2005 23:13:59 +0000 (GMT) (envelope-from tms3@fskklaw.com) Received: from fuckms.fsklaw.net [192.168.64.2] by thor-new.fsklaw.com (ArGoSoft Mail Server Pro for WinNT/2000/XP, Version 1.8 (1.8.6.0)); Tue, 25 Jan 2005 15:15:05 -0800 Message-ID: <41F6D2F2.9070605@fskklaw.com> Date: Tue, 25 Jan 2005 15:14:58 -0800 From: "Thomas M. Skeren III" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Reichert References: <20050124232119.66192.qmail@web30406.mail.mud.yahoo.com> <20050125193419.GJ80512@numachi.com> In-Reply-To: <20050125193419.GJ80512@numachi.com> X-ArGoMail-Authenticated: tms3 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-net@freebsd.org cc: Mihai Nitulescu Subject: Re: public ip address behind nat X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 23:14:00 -0000 Brian Reichert wrote: >On Mon, Jan 24, 2005 at 03:21:19PM -0800, Mihai Nitulescu wrote: > > >>In the LAN i have the other machine application.example.com >>I have some Public IP`s from my ISP : >> >>193.231.43.25-30 >>255.255.255.248 >> >>I want to assign to application.example.com 193.231.43.27 and to route this ip trough nat.example.com >> >>Any ideea how can i do that ? >> >> I'm having problems with your setup. Is Application.example.com at 193.531.43.27 or is it on the lan with an internal address? If it's internal, then machines on the lan can see the internal IP, so there's no reason for it to have a public address. If machines outside the lan need to get to app.ex.com, then use natd_flags in rc.conf and point the ports you need opened on app to the local addy of app, and use the NAT's external addy for the external users of app. That would be the easiest way if you don't want to give an external addy to app. Of course the easiest way is to just give app an external addy and plug it into the ISP supplied router. Unless app is a M$ box, of course. > >See 'redirect_address' in natd(8). > >I believe you'll also need to assign your public IPs to the external >interface of your NAT box. > >I have a similar setup, but I need to review just what I've done >to make that work... > > > >>Please help. >> >>Regards, >> >>Mihai >> >> > > >