Date: Sat, 17 Feb 2001 19:38:19 -0600 (CST) From: Brennan Stehling <brennan@offwhite.net> To: Bill Moran <wmoran@mail.iowna.com> Cc: cjclark@alum.mit.edu, Cliff Sarginson <cliff@raggedclown.net>, questions@FreeBSD.ORG Subject: Re: natd & failed to write packet back Message-ID: <Pine.BSF.4.21.0102171934590.56304-100000@home.offwhite.net> In-Reply-To: <3A6455B2.F797877F@mail.iowna.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I am unsure if you have fixed this problem yet. I had the same problem
and perhaps you have the same issues.
I was running Netatalk to do AppleShare/IP on a FreeBSD router and trying
to have it run on both the public and private interfaces. It kept on
spewing out this error message and finally I simply dropped AppleShare/IP
from the public interface and kept it all on the private network. That
stopped the error messages.
Perhaps blocking all traffic to private addresses through the public
interface would work, but I do not know how to do that. That was a
suggestion by someone else on this thread. Perhaps that person can
elaborate with a config example.
Brennan Stehling - software developer and system administrator
my projects:
home.offwhite.net (free personal hosting)
www.greasydaemon.com (bsd search)
On Tue, 16 Jan 2001, Bill Moran wrote:
> "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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0102171934590.56304-100000>