Date: Sat, 2 Dec 2000 00:46:12 -0800 From: "Crist J . Clark" <cjclark@reflexnet.net> To: Ray Slakinski <thrawn@hub.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NATD[88] Message-ID: <20001202004612.N99903@149.211.6.64.reflexcom.com> In-Reply-To: <007201c05c34$e91d7310$0a00a8c0@CR883166A>; from thrawn@hub.org on Sat, Dec 02, 2000 at 02:53:08AM -0500 References: <007201c05c34$e91d7310$0a00a8c0@CR883166A>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 02, 2000 at 02:53:08AM -0500, Ray Slakinski wrote: > Greetings all! > > I am using Freebsd 4.0-RELEASE and my network appears to be running like a > champ, all my internal machines can view the internet, and the internet can > view my machine. > > here comes the problem, I looked in my logs and noticed this > > NATD[88] : failed to write packet back (Host is down) > > This occures repeatedly in /var/log/messages and to say the least is very > confusing. I have told the firewall ruleset to be open, and I get the same > results. Looks like natd(8) failed to send out a packet because a host is down. Damn those confusing messages, huh? That means that you are trying to send packets to a _local_ machine that is either (a) not there at all, (b) not up, or (c) not communicating properly with the NAT box at the data layer. Can you figure out what host you are trying to reach that is not responding? One way others have been able to track down the problem is to sniff the network for unanswered ARP queries. Your box should be generating a lot for this missing host. -- Crist J. Clark cjclark@alum.mit.edu 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?20001202004612.N99903>