Date: Fri, 11 Jul 2003 19:25:21 +0200 From: Roman Neuhauser <dev-null@bellavista.cz> To: Brett Glass <brett@lariat.org> Cc: questions@freebsd.org Subject: Re: Dead natd -> dead system Message-ID: <20030711172521.GC35136@freepuppy.bellavista.cz> In-Reply-To: <200307101957.NAA01395@lariat.org> References: <200307101957.NAA01395@lariat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
# brett@lariat.org / 2003-07-10 13:57:33 -0600:
> While working with a FreeBSD system this afternoon, I did something which killed
> natd (the NAT daemon), which was processing packets in the usual way via ipfw
> and a divert socket.
>
> The result? Network communications on the system simply went dead.
>
> It seems to me that ipfw should be able to "self-heal" (that is, bypass the
> rule) or reinvoke a daemon that's attached to a divert socket. Otherwise,
> the process that's attached to the socket becomes an Achilles' heel for
> the whole system. Crash it for any reason, and the system's offline.
>
> Ideas?
sysutils/daemontools ?
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030711172521.GC35136>