From owner-freebsd-questions Thu Sep 13 17:29:24 2001 Delivered-To: freebsd-questions@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id 1848F37B40B for ; Thu, 13 Sep 2001 17:29:21 -0700 (PDT) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f8E0TFZ35690; Thu, 13 Sep 2001 19:29:15 -0500 (CDT) (envelope-from nick@rogness.net) Date: Thu, 13 Sep 2001 19:29:15 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: Sheldon Hearn Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NATD address_redirect kills host's connectivity In-Reply-To: <61490.1000421725@axl.seasidesoftware.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 - 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