NATD remote management

Minnesota Slinky mnslinky at
Sat Dec 13 16:54:26 PST 2003


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
AdTech Integrated Systems, Inc
(612) 998-3588

-----Original Message-----
From: owner-freebsd-questions at
[mailto:owner-freebsd-questions at] On Behalf Of Jack L. Stone
Sent: Saturday, December 13, 2003 10:26 AM
To: freebsd-questions at
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

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

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,

SageOne Net
jackstone at _______________________________________________
freebsd-questions at mailing list
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at"

More information about the freebsd-questions mailing list