From owner-freebsd-net Wed Nov 4 05:47:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24907 for freebsd-net-outgoing; Wed, 4 Nov 1998 05:47:03 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24902 for ; Wed, 4 Nov 1998 05:47:00 -0800 (PST) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id IAA27924; Wed, 4 Nov 1998 08:46:47 -0500 (EST) Date: Wed, 4 Nov 1998 08:46:47 -0500 (EST) To: Open Systems Networking cc: freebsd-net@FreeBSD.ORG Subject: Re: NATD error question. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 3 Nov 1998, Open Systems Networking wrote: > natd: failed to write packet back (permission denied) I've got a similar question... I recently setup a fbsd box doing NAT for an internal (Windows/Mac-based) LAN. I want to eventually implement IPFW rules, but for now I'm just running an 'open' configuration to make adressing NAT misconfigurations easier for me. I see a similar message, natd: failed to write packet back (host is down) It sounds like this could be ipfw-related (misconfiguration) as well, but as I said above, I'm currently running an 'open' policy. Is there something I need to specifically allow from my internal net (I've seen NetBIOS mentioned) that the typical 'pass all from any to any' open policy does not address? Later, -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message