From owner-freebsd-net Sat Jan 26 15:32: 2 2002 Delivered-To: freebsd-net@freebsd.org Received: from artemis.drwilco.net (diana.drwilco.net [66.48.127.79]) by hub.freebsd.org (Postfix) with ESMTP id 0901237B404 for ; Sat, 26 Jan 2002 15:31:58 -0800 (PST) Received: from ceres.drwilco.net (docwilco.xs4all.nl [213.84.68.230]) by artemis.drwilco.net (8.11.6/8.11.6) with ESMTP id g0QNViw44671 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO); Sat, 26 Jan 2002 18:31:46 -0500 (EST) (envelope-from drwilco@drwilco.net) Message-Id: <5.1.0.14.0.20020127002514.01d56978@mail.drwilco.net> X-Sender: lists@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 27 Jan 2002 00:41:23 +0100 To: Clemens Hermann , BSD NET-List From: "Rogier R. Mulhuijzen" Subject: Re: natd restart In-Reply-To: <20020126234617.C267@idefix.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 23:46 26-1-2002 +0100, Clemens Hermann wrote: >Hi, > >Is there a way to get natd to reload the config-file without terminating? >The only way I found is to stop natd and then start it again. I am afraid that natd is extremely simple, and does not allow any control after it has been started. >As the natd-config changes frequently here (we are changing the used network >and we misuse natd to help us) I expect problems when just shuting down natd >in a heavily used environment. What sort of changes are you talking about here? Maybe there's a different way of going about it. >If I got it right natd does not keep track about state but anyway if I stop >and start natd frequently I certainly will lose connections, right? natd does keep state (in libalias, which is statically linked into it). Killing natd would thus clean all your state info. >I could not find a way to HUP natd, neither to change its behaviour during >runtime. >Is there a way to solve the issue or does the problem I see not exist and >in reality nobody will notice anything if natd is stopped and restarted? I use natd here at home and all translated connections get the boot when I kill and restart natd. Connections that are only routed survive fine (since they get no translation). Doc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message