From owner-freebsd-questions Tue Jan 16 6:11:21 2001 Delivered-To: freebsd-questions@freebsd.org Received: from clmboh1-smtp3.columbus.rr.com (unknown [65.24.0.112]) by hub.freebsd.org (Postfix) with ESMTP id 009B237B404 for ; Tue, 16 Jan 2001 06:11:04 -0800 (PST) Received: from mail.iowna.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38]) by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id f0GE8e718602; Tue, 16 Jan 2001 09:08:41 -0500 (EST) Message-ID: <3A6455B2.F797877F@mail.iowna.com> Date: Tue, 16 Jan 2001 09:07:46 -0500 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: cjclark@alum.mit.edu Cc: Cliff Sarginson , questions@FreeBSD.ORG Subject: Re: natd & failed to write packet back References: <20010115234039.L97980@rfx-64-6-211-149.users.reflexco> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Crist J. Clark" wrote: > > In a similar vain, what does the above message indicate but accompanied > > by a "permission denied" as the reason ? > > Doh! Thanks for catching that. I described what 'permission denied' > means. When it says 'host is down,' well... it means that the host the > packet is destined for is down. It must be a host on the local network > to get that message. Well, this helps & not. So, apparently a host on the local (you mean internal, private ips?) network is down. Howerver, it started communicating before it went down. I wouldn't worry, but the fact that it's happening so much. It would be nice if it would tell me _which_ host is down. I guess it could have to do with the Macs going into sleep mode. These folks have a tendency to leave programs running (even after they leave for the day) If a browser were looking at something and went into sleep mode before the exchange completed, this could happen. But that's really pretty far-fetched and it's just a theory. Hmmm ... the mystery continues. Any hints on how to diagnose this? It'd be difficult to isolate the packets that are causing it when there's no indication of IP or port #. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message