From owner-freebsd-questions Wed Feb 17 9:46:22 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mars.aros.net (mail.aros.net [207.173.16.20]) by hub.freebsd.org (Postfix) with ESMTP id C4456111E7 for ; Wed, 17 Feb 1999 09:46:17 -0800 (PST) (envelope-from razorwit@aros.net) Received: from LP (laptop.aros.net [207.173.16.127]) by mars.aros.net (8.9.2/8.9.2) with SMTP id KAA26913 for ; Wed, 17 Feb 1999 10:46:17 -0700 (MST) From: "Dean" To: freebsd-questions@freebsd.org Date: Wed, 17 Feb 1999 10:41:37 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: natd Reply-To: razorwit@aros.net X-mailer: Pegasus Mail for Win32 (v3.01b) Message-Id: <19990217174620.C4456111E7@hub.freebsd.org> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using a 3.0-RELEASE version of freeBSD running NATD. About once a night natd core dumps on me and the machine must reboot before it will run properly again. The NICs in the machine are both intel 10/100 cards (fxp) and the box seems to run fine except for that (/var/log/messages and ipfw.pick-a-day don't show any problems). Anyone heard of a hardware problem causing NATD to dump core (like a bad NIC or memory...)? Alternately, anyone else have any ideas what may be causing it? Thanks Dean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message