From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 6 06:29:20 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C075D16A4B3 for ; Mon, 6 Oct 2003 06:29:20 -0700 (PDT) Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id E34C443FE1 for ; Mon, 6 Oct 2003 06:29:12 -0700 (PDT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.3p3/8.12.3) with ESMTP id h96DSx4Z072775 for ; Mon, 6 Oct 2003 17:28:59 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.3p3/8.12.3/Submit) id h96DSwJo072774 for freebsd-hackers@freebsd.org; Mon, 6 Oct 2003 17:28:58 +0400 (MSD) (envelope-from yar) Date: Mon, 6 Oct 2003 17:28:57 +0400 From: Yar Tikhiy To: freebsd-hackers@freebsd.org Message-ID: <20031006132857.GA71659@comp.chem.msu.su> References: <20031004235400.GA20943@ussenterprise.ufp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031004235400.GA20943@ussenterprise.ufp.org> User-Agent: Mutt/1.5.3i Subject: Re: Changing the NAT IP on demand? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2003 13:29:20 -0000 On Sat, Oct 04, 2003 at 07:54:00PM -0400, Leo Bicknell wrote: > > That, by itself, is not hard. Here's the trick. I want the switch > to be seamless. That is, if NAT is translating to ISP #1 and the > application says switch to #2 the existing translations to #1 (until > they go away naturally) should be kept, while new ones go to #2. Just a random thought: If natd(8) were taught to change its default alias address on the fly (it's just a single variable,) then the desired effect would be achieved exactly. That's because any session already having its own entry in natd's aliasing table would use its old alias address kept in the entry. BTW, one could switch between even more than 2 external connections in that manner. And that's just a step away from session-aware load-balancing with natd(8). -- Yar