Date: Fri, 13 Apr 2001 13:05:22 -0500 From: "Thomas T. Veldhouse" <veldy@veldy.net> To: "Gordon Tetlow" <gordont@bluemtn.net> Cc: <freebsd-stable@freebsd.org> Subject: Re: natd[232]: failed to write packet back (Permission denied) Message-ID: <00a601c0c444$4ef9fc40$3028680a@tgt.com> References: <Pine.BSF.4.33.0104131101380.60994-100000@sdmail0.sd.bmarts.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I was using stateful firewalling. I get even more errors. Oddly, whatever is causing it now happens in bursts of two every 12 minutes. I have not figured it out -- really annoying. The default "SIMPLE" firewall also causes it. That should not be -- so I would call that a bug in the /etc/rc.firewall script at the very least. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Gordon Tetlow" <gordont@bluemtn.net> To: "Thomas T. Veldhouse" <veldy@veldy.net> Cc: <freebsd-stable@FreeBSD.ORG> Sent: Friday, April 13, 2001 1:03 PM Subject: Re: natd[232]: failed to write packet back (Permission denied) > But, if you use the default firewall rules, *all* packets get put through > natd, not just lan traffic, but incoming, and loopback traffic as well. > > I used to have this problem, but when I rewrote my firewall rules to use > stateful firewalling, it disappeared. > > -gordon > > On Fri, 13 Apr 2001, Thomas T. Veldhouse wrote: > > > As an addendum -- I get these messages even when there is NO activity on the > > LAN -- so natd is not even being used by any client. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00a601c0c444$4ef9fc40$3028680a>