Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Oct 2000 15:11:51 +0700
From:      Roger Merritt <mcrogerm@stjohn.ac.th>
To:        questions@freebsd.org
Subject:   Re: natd ; Host is dowm ???
Message-ID:  <3.0.6.32.20001003151151.008c8100@stjohn.stjohn.ac.th>
In-Reply-To: <20001003010159.Q25121@149.211.6.64.reflexcom.com>
References:  <39D880BE.F7499B19@home.se> <39D880BE.F7499B19@home.se>

next in thread | previous in thread | raw e-mail | index | archive | help
At 01:02 AM 10/3/00 -0700, you wrote:
>On Mon, Oct 02, 2000 at 02:34:06PM +0200, Nash wrote:
>> Hi,
>> 
>> My server is issuing an error message that has got me blowing my
>> head off on!! 
>> 
>> ... natd[131]: failed to write packet back (Host is down)
>> 
>> Does anyone know what "host" is meant here?
>
>Same thing it usually does, another machine (interface) on the
>LAN. natd is telling you that after processing a packet, it cannot be
>sent to the machine it is addressed to because the "host is down."
>What that means is that the system cannot get the data link layer
>address for the IP address in question.
>
>There is not enough information for a further diagnosis.
>-- 
>Crist J. Clark                           cjclark@alum.mit.edu
>

Well, that's the problem, isn't it? I keep getting the same messages
(fewer now that I got Samba better configured). I've never been able to
figure out what host is meant or *why* natd can't connect with it or
why natd wants to in the first place. Is there any way to force natd to
give more info? Even though the messages don't bother me as much as
they used to they still end up filling up the kernel message buffer and
overwriting the boot messages (apparently in defiance of syslogd).
-- 
Roger



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?3.0.6.32.20001003151151.008c8100>