From owner-freebsd-questions@FreeBSD.ORG Sat Dec 13 16:54:26 2003 Return-Path: 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 D0B5916A4CE for ; Sat, 13 Dec 2003 16:54:26 -0800 (PST) Received: from smtp104.mail.sc5.yahoo.com (smtp104.mail.sc5.yahoo.com [66.163.169.223]) by mx1.FreeBSD.org (Postfix) with SMTP id CBEA243DF8 for ; Sat, 13 Dec 2003 16:48:01 -0800 (PST) (envelope-from mnslinky@yahoo.com) Received: from unknown (HELO Nomad) (mnslinky@66.41.18.160 with login) by smtp104.mail.sc5.yahoo.com with SMTP; 14 Dec 2003 00:46:55 -0000 From: "Minnesota Slinky" To: "'Jack L. Stone'" , Date: Sat, 13 Dec 2003 18:45:41 -0600 Message-ID: <004901c3c1db$9dc8d890$6401a8c0@Nomad> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <3.0.5.32.20031213102548.01e3d240@10.0.0.10> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: RE: NATD remote management X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 00:54:26 -0000 Jack, What I find usually works for me is a simple script that checks to see if natd is running. If not, it reloads natd after flusshing all the rules. I usually set this script to run every 5 minutes or so. You can change that to match your needs. Eric F Crist President AdTech Integrated Systems, Inc (612) 998-3588 -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Jack L. Stone Sent: Saturday, December 13, 2003 10:26 AM To: freebsd-questions@freebsd.org Subject: NATD remote management Dear list: I manage a remote gateway/nat/router/fw server where it is not convenient for anyone to go downtown to the colo and do reboots. I've managed to do everything here remotely from my own console, including reboots when updating the OS requires it -- that is except when reconfiguring the natd.conf file to add another forwarding service. I can reboot and it comes up okay, but rather would avoid a reboot. BUT, if I try to kill/restart the natd daemon remotely, it kills my SSH session -- no restart of NATD -- cannot log back in and that means a 30-min trip for someone to the colo. That gets old and rather just reboot which is a lot less inconvenient. Obviously, when I do the kill of natd, it disconnects my SSH session and I can't restart the daemon so it can reread the natd.conf file for my changes. I've tried a background script, but that hasn't worked either. Perhaps a second session would stay alive.... either SSH or even a telnet session just for the duration for this event??? Or a better background script...?? I'd rather not do any uninformed guessing/gambling on different techniques to cause a lock out. There's probably a simple answer and hope someone will remind me what it is.... Many thanks & Happy Holidays to the list. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"