From owner-freebsd-questions Tue Jan 16 15:51: 4 2001 Delivered-To: freebsd-questions@freebsd.org Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93]) by hub.freebsd.org (Postfix) with ESMTP id 5F24A37B402 for ; Tue, 16 Jan 2001 15:50:44 -0800 (PST) Received: from parmenides.utp.xnet by smtp.hccnet.nl via uds45-123.dial.hccnet.nl [193.173.123.45] with ESMTP id AAA02371 (8.8.5/1.13); Wed, 17 Jan 2001 00:50:40 +0100 (MET) Received: by parmenides.utp.xnet (Postfix, from userid 1005) id 7C381142; Wed, 17 Jan 2001 00:49:27 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by parmenides.utp.xnet (Postfix) with ESMTP id 35B66131; Wed, 17 Jan 2001 00:49:27 +0100 (CET) Date: Wed, 17 Jan 2001 00:49:27 +0100 (CET) From: Janko van Roosmalen X-Sender: acs@parmenides.utp.xnet To: Bill Moran Cc: questions@freebsd.org Subject: Re: natd & failed to write packet back In-Reply-To: <3A63C754.AEA088A@mail.iowna.com> 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 On Mon, 15 Jan 2001, Bill Moran wrote: > A proxy/firewall/nat box I recently set up is constantly spewing out an > error from natd: > failed to write packet back [host is down] > > What exactly is happening here? This is pretty ambiguous, I mean - what > host? It seems to indicate that a machine that was using natd went > offline before the communication completed, but it's occurring > constantly (I see the message a few times a minute at times) > > Is this indicative of any type of problem, misconfig? On a FreeBSD 3.2 box with ISDN4BSD I had a lot of similar messages but then the reason was "cannot assign requested address". In my case it was the isdn daemon that broke off the connection after a few minutes of inactivity, while there was still something going on. I gathered more info by having the natd daemon log its messages to a file in /var/log. On a 3.2 box I added these 2 lines to /etc/syslog.conf: !natd *.* /var/log/natd.log Created an empty natd.log: touch /var/log/natd.log And sent a -HUP signal to the natd daemon. From the natd.log (with date and hostname removed): 07:21:21 natd[120]: Aliasing to 0.0.0.0, mtu 1500 bytes 07:21:51 natd[120]: Aliasing to 193.173.123.59, mtu 1500 bytes 07:34:21 natd[120]: Aliasing to 0.0.0.0, mtu 1500 bytes 07:34:21 natd[120]: failed to write packet back (Can't assign requested address) 07:34:21 natd[120]: failed to write packet back (Can't assign requested address) 07:34:24 natd[120]: Aliasing to 193.173.123.54, mtu 1500 bytes 20:11:27 natd[120]: Aliasing to 193.173.123.181, mtu 1500 bytes 20:17:11 natd[120]: Aliasing to 0.0.0.0, mtu 1500 bytes 20:17:11 natd[120]: failed to write packet back (Can't assign requested address) 20:17:15 natd[120]: Aliasing to 193.173.123.15, mtu 1500 bytes 20:19:44 natd[120]: Aliasing to 0.0.0.0, mtu 1500 bytes 20:19:44 natd[120]: failed to write packet back (Can't assign requested address) 20:20:17 last message repeated 6 times 20:20:44 natd[120]: Aliasing to 193.173.123.175, mtu 1500 bytes ===Janko van Roosmalen - Vught - Netherlands=== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message