From owner-freebsd-stable  Fri Apr 13 11: 4:54 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155])
	by hub.freebsd.org (Postfix) with ESMTP id 97EA337B424
	for <freebsd-stable@FreeBSD.ORG>; Fri, 13 Apr 2001 11:04:52 -0700 (PDT)
	(envelope-from gordont@bluemtn.net)
Received: from localhost (gordont@localhost)
	by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f3DI3n268655;
	Fri, 13 Apr 2001 11:03:49 -0700 (PDT)
Date: Fri, 13 Apr 2001 11:03:49 -0700 (PDT)
From: Gordon Tetlow <gordont@bluemtn.net>
X-X-Sender:  <gordont@sdmail0.sd.bmarts.com>
To: "Thomas T. Veldhouse" <veldy@veldy.net>
Cc: <freebsd-stable@FreeBSD.ORG>
Subject: Re: natd[232]: failed to write packet back (Permission denied)
In-Reply-To: <002b01c0c43b$95b2ee20$3028680a@tgt.com>
Message-ID: <Pine.BSF.4.33.0104131101380.60994-100000@sdmail0.sd.bmarts.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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