From owner-freebsd-questions Mon Oct 2 15:48:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from pop.hccnet.nl (pop.hccnet.nl [193.172.127.94]) by hub.freebsd.org (Postfix) with ESMTP id 3972937B503 for ; Mon, 2 Oct 2000 15:48:12 -0700 (PDT) Received: from parmenides.utp.net by pop.hccnet.nl via uds181-123.dial.hccnet.nl [193.173.123.181] with ESMTP id AAA20197 (8.8.5/1.13); Tue, 3 Oct 2000 00:48:10 +0200 (MET DST) Received: from localhost (janko@localhost) by parmenides.utp.net (8.9.3/8.9.3) with ESMTP id AAA01160; Tue, 3 Oct 2000 00:48:11 +0200 (CEST) (envelope-from janko@compuserve.com) X-Authentication-Warning: parmenides.utp.net: janko owned process doing -bs Date: Tue, 3 Oct 2000 00:48:10 +0200 (CEST) From: Janko van Roosmalen X-Sender: janko@parmenides.utp.net To: Nash Cc: freebsd-questions@FreeBSD.ORG Subject: Re: natd ; Host is dowm ??? In-Reply-To: <39D880BE.F7499B19@home.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I configured ISDN dial-on-demand on my FreeBSD 3.2 system. I get similar messages. I think they are caused by a time-out. When there is no activity for some time the isdn demon breaks the connection, the isdn card looses its assigned ip address. "natd" reports it as "aliasing to 0.0.0.0". From my natd.log (my daughter was reading her yahoo email, +-20.00 hr is internet prime time here in Holland) : Oct 1 20:08:28 natd[120]: Aliasing to 193.173.123.100, mtu 1500 bytes Oct 1 20:16:32 natd[120]: Aliasing to 0.0.0.0, mtu 1500 bytes Oct 1 20:16:32 natd[120]: failed to write packet back (Can't assign requested address) Oct 1 20:16:50 last message repeated 8 times Oct 1 20:16:53 natd[120]: Aliasing to 193.173.123.49, mtu 1500 bytes At 20.08.28 a connection is made. Because she was composing her email replies the connection was broken at 20.16.32. At about the same time she wanted to send off her email. Because it was very busy it took some about 21 seconds to get connected at 20:16:53. Normally it takes only 3 seconds. Why don't you make an entry in (new)syslog.conf for natd and see if the resulting log will give you a clue to what is going in your case? Janko van Roosmalen - Vught - Netherlands > > 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? > The message comes up randomly and comes in very large occurrences. > It really doesn't seem to be affecting anything as far as the > connection speed is concerned; BUT IT SURE IS IRRITATING ME!!! It > has been filling up my "/var/log/messages" file for the past few > months, and I seriously considering writing a program just to > prevent the message itself from showing up. > > I use natd to make my server into a router and have an internal > network behind it. Also have a firewall, DNS, http-daemons, > FTP-daemons on the same machine. I've tried removing any and/or all > of these other daemons from the machine to see if it effects this > message; but in vein. > > The only other thing I've though of is that, it seems like someone > else also has an internal network in our subnet and is probably > sending ARP-requests externally?!? I frankly don't understand this > thing and would appreciate any suggestions whatsoever, and > especially if someone can tell me how to find out "which/what" > -host the error message is talking about? > > Thank you beforehand, > N.S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message