From owner-freebsd-questions@FreeBSD.ORG Fri Jul 14 20:17:38 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3D8416A4DE for ; Fri, 14 Jul 2006 20:17:38 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id F35C143D49 for ; Fri, 14 Jul 2006 20:17:37 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 6F6715E6D; Fri, 14 Jul 2006 16:17:37 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k6f0YNsokYey; Fri, 14 Jul 2006 16:17:36 -0400 (EDT) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id AC8BA5D49; Fri, 14 Jul 2006 16:17:36 -0400 (EDT) In-Reply-To: <44B7F7FA.8050903@nyi.net> References: <44B7F7FA.8050903@nyi.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <55E4C410-41FD-4028-AF53-5A5E8A517C52@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Fri, 14 Jul 2006 16:17:35 -0400 To: Darek M X-Mailer: Apple Mail (2.752.2) Cc: freebsd-questions@freebsd.org Subject: Re: Updating system's natd config from natd.conf X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 20:17:38 -0000 On Jul 14, 2006, at 4:00 PM, Darek M wrote: > What is the procedure to make active changes made to /etc/natd.conf? > > Sometimes, restarting the natd process with an HUP drops my > connection. Other times the restart didn't seem to make any > difference. The only way I've ever updated natd rules was to > restart the server and never was able to find anything relating to > this topic online. Basicly, you need to kill and restart natd right now, and doing so will lose track of any active state for currently-open connections. Natd dies when it gets a SIGHUP, but I've always wanted to extend its signal handler to trap SIGHUP and re-read the config file. -- -Chuck