From owner-freebsd-questions@FreeBSD.ORG Sat Dec 13 08:25:51 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 A203C16A4CE for ; Sat, 13 Dec 2003 08:25:51 -0800 (PST) Received: from sage-one.net (adsl-65-71-135-137.dsl.crchtx.swbell.net [65.71.135.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6001343D09 for ; Sat, 13 Dec 2003 08:25:50 -0800 (PST) (envelope-from jackstone@sage-one.net) Received: from sagea (sagea.sage-american [10.0.0.3]) by sage-one.net (8.12.8p2/8.12.8) with SMTP id hBDGPmkX044379 for ; Sat, 13 Dec 2003 10:25:49 -0600 (CST) (envelope-from jackstone@sage-one.net) Message-Id: <3.0.5.32.20031213102548.01e3d240@10.0.0.10> X-Sender: jackstone@10.0.0.10 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 13 Dec 2003 10:25:48 -0600 To: freebsd-questions@freebsd.org From: "Jack L. Stone" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, hits=-4.7 required=4.5 tests=AWL,BAYES_00 autolearn=ham version=2.60-sageame.rules_v1 X-Spam-Checker-Version: SpamAssassin 2.60-sageame.rules_v1 (1.212-2003-09-23-exp) on sage-one.net Subject: 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: Sat, 13 Dec 2003 16:25:51 -0000 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