Date: Thu, 25 Oct 2001 09:30:04 +0200 From: "Patrick O'Reilly" <patrick@mip.co.za> To: "Forrest Aldrich" <forrie@forrie.com>, <freebsd-stable@FreeBSD.ORG> Subject: RE: natd error message, upon bootup Message-ID: <NDBBIMKICMDGDMNOOCAIGECBDMAA.patrick@mip.co.za> In-Reply-To: <5.1.0.14.2.20011024113047.01f4de58@216.67.14.69>
next in thread | previous in thread | raw e-mail | index | archive | help
Forrest, I have seen the same happen with on-board Serial cards if the interface goes down due to a line problem. In other words, my natd interface is a Serial WAN card hooked directly to the data line. If the line goes down or flaps, then the interface goes 'down'. Now, natd attempts to write out packets to that interface, but its down, and hence the problem. If you are seeing the message briefly just after start-up, perhaps the problem is that your natd interface is taking some time to get 'up', and natd has started trying to use it before it's up? Patrick. > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Forrest Aldrich > Sent: 24 October 2001 17:39 > To: freebsd-stable@FreeBSD.ORG > Subject: natd error message, upon bootup > > > I've been seeing this prior to 4.4, and am not sure it's even a problem; > however, after the system boots up, and just after the first external > packets are routed, I see this message in the syslog: > > Oct 24 11:19:08 machinename natd[202]: failed to write packet > back (Host is > down) > > There's no other indication of a problem thereafter; this started > happening > a while ago, after I upgraded to 4.3. This is now 4.4-STABLE. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBIMKICMDGDMNOOCAIGECBDMAA.patrick>