# [EMAIL PROTECTED] / 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
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
On Thu, 10 Jul 2003, Brett Glass wrote:
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
On Thu, 10 Jul 2003 16:56:12 -0400 (EDT)
Matthew Emmerton [EMAIL PROTECTED] wrote:
On Thu, 10 Jul 2003, Brett Glass wrote:
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
On Fri, 11 Jul 2003, Vulpes Velox wrote:
On Thu, 10 Jul 2003 16:56:12 -0400 (EDT)
Matthew Emmerton [EMAIL PROTECTED] wrote:
On Thu, 10 Jul 2003, Brett Glass wrote:
While working with a FreeBSD system this afternoon, I did something which killed
natd (the NAT daemon), which was
