From owner-freebsd-net@FreeBSD.ORG Tue Jan 25 01:16:52 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 0A92516A4CE for ; Tue, 25 Jan 2005 01:16:52 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id B446843D39 for ; Tue, 25 Jan 2005 01:16:51 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id F327C6520E; Tue, 25 Jan 2005 01:16:50 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08163-01-3; Tue, 25 Jan 2005 01:16:50 +0000 (GMT) Received: from empiric.dek.spc.org (unknown [213.210.24.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 735ED651F7; Tue, 25 Jan 2005 01:16:50 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id DC2166383; Tue, 25 Jan 2005 01:18:00 +0000 (GMT) Date: Tue, 25 Jan 2005 01:18:00 +0000 From: Bruce M Simpson To: Mihai Nitulescu Message-ID: <20050125011800.GC47638@dhcp120.icir.org> Mail-Followup-To: Mihai Nitulescu , freebsd-net@freebsd.org References: <20050124232119.66192.qmail@web30406.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050124232119.66192.qmail@web30406.mail.mud.yahoo.com> cc: freebsd-net@freebsd.org 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 01:16:52 -0000 On Mon, Jan 24, 2005 at 03:21:19PM -0800, Mihai Nitulescu wrote: > I want to assign to application.example.com 193.231.43.27 and to route this ip trough nat.example.com If you have control over the NAT device, you could set up a point-to-point tunnel from the NAT device to the machine in the NAT domain; this would preserve the public IP address but would require additional routing setup (assuming that the public subnet is routed by the ISP to the NAT device). Hope this helps, BMS