Date: Sat, 13 Dec 2003 18:45:41 -0600 From: "Minnesota Slinky" <mnslinky@yahoo.com> To: "'Jack L. Stone'" <jackstone@sage-one.net>, <freebsd-questions@freebsd.org> Subject: RE: NATD remote management Message-ID: <004901c3c1db$9dc8d890$6401a8c0@Nomad> In-Reply-To: <3.0.5.32.20031213102548.01e3d240@10.0.0.10>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004901c3c1db$9dc8d890$6401a8c0>