From owner-freebsd-questions Thu Sep 13 15:55:41 2001 Delivered-To: freebsd-questions@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 3A92737B40A for ; Thu, 13 Sep 2001 15:55:37 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 15hfOH-000Fzn-00; Fri, 14 Sep 2001 00:55:25 +0200 From: Sheldon Hearn To: Nick Rogness Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NATD address_redirect kills host's connectivity In-reply-to: Your message of "Thu, 13 Sep 2001 17:14:07 EST." Date: Fri, 14 Sep 2001 00:55:25 +0200 Message-ID: <61490.1000421725@axl.seasidesoftware.co.za> 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 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? Anyway, thanks for the quick response. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message