From owner-freebsd-questions Sat Jan 27 11:50:33 2001 Delivered-To: freebsd-questions@freebsd.org Received: from winf.htu.tuwien.ac.at (winf.htu.tuwien.ac.at [128.131.95.2]) by hub.freebsd.org (Postfix) with ESMTP id 2C6A937B401 for ; Sat, 27 Jan 2001 11:50:17 -0800 (PST) Received: from acm.org (fswinf1 [192.168.0.11]) by winf.htu.tuwien.ac.at (Postfix) with ESMTP id 7E7BE5D1F; Sat, 27 Jan 2001 20:50:15 +0100 (CET) Message-ID: <3A732677.6618BCE4@acm.org> Date: Sat, 27 Jan 2001 20:50:15 +0100 From: "Klaus A. Brunner" X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Cliff Sarginson , questions@FreeBSD.ORG Cc: Bill Moran Subject: Re: natd & failed to write packet back Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (referring to on -questions) > > On Mon, Jan 15, 2001 at 11:00:20PM -0500, Bill Moran wrote: > > > A proxy/firewall/nat box I recently set up is constantly spewing > > > out an error from natd: > > > failed to write packet back [host is down] > > ... > In a similar vain, what does the above message indicate but > accompanied by a "permission denied" as the reason ? This has already been discussed numerous times (search the list archives). I've been struggling with this problem, too. In my case the culprit turned out to be a misconfigured Samba, broadcasting onto a subnet explicitly blocked by ipfw (actually, that subnet didn't even exist). To find out, I patched /usr/src/sbin/natd.c and made the error message a little more verbose. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=24683 Klaus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message