Date: Thu, 13 Sep 2001 19:29:15 -0500 (CDT) From: Nick Rogness <nick@rogness.net> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NATD address_redirect kills host's connectivity Message-ID: <Pine.BSF.4.21.0109131926160.35666-100000@cody.jharris.com> In-Reply-To: <61490.1000421725@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Sep 2001, Sheldon Hearn wrote: > > > On Thu, 13 Sep 2001 17:14:07 EST, Nick Rogness wrote: > > > > # Sheldon's workstation > > > redirect_address 10.0.0.2 196.31.7.201 > > > ---- > > > > Looks OK. > > So much so that I've since gotten it to work without making any > changes of which I'm aware. > > Is it possible that starting natd too soon after another natd process > dies could cause a problem? The process _definitely_ died, but > perhaps there are dynamic ipfw rules that take time to disappear or > something? Yes. It takes a certain amount of time (I believe 10 sec for me) for the natd process to die off. Nick Rogness <nick@rogness.net> - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0109131926160.35666-100000>