From owner-freebsd-questions Fri Sep 25 10:35:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06755 for freebsd-questions-outgoing; Fri, 25 Sep 1998 10:35:56 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from news.mtu.edu (news.mtu.edu [141.219.70.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06707 for ; Fri, 25 Sep 1998 10:35:36 -0700 (PDT) (envelope-from dmbrodbe@mtu.edu) Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id NAA19705 for ; Fri, 25 Sep 1998 13:35:27 -0400 (EDT) Received: from techsrv1.tech.mtu.edu (dmbrodbe@techsrv1.tech.mtu.edu [141.219.23.7]) by mtu.edu (8.8.8/8.8.8) with ESMTP id NAA08390 for ; Fri, 25 Sep 1998 13:35:26 -0400 (EDT) Received: from localhost (dmbrodbe@localhost) by techsrv1.tech.mtu.edu (8.8.8/8.8.7/mturelay-1.2) with SMTP id NAA02393 for ; Fri, 25 Sep 1998 13:35:23 -0400 (EDT) X-Authentication-Warning: techsrv1.tech.mtu.edu: dmbrodbe owned process doing -bs Date: Fri, 25 Sep 1998 13:35:22 -0400 (EDT) From: "David M. Brodbeck" X-Sender: dmbrodbe@techsrv1.tech.mtu.edu To: freebsd-questions@FreeBSD.ORG Subject: natd dies with signal 11 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'm having a problem with natd, and a search of the mailing list archives has turned up kind of empty. First, the details: I'm running 1998-09-23-BETA, but I've had the problem since I started my installation with 1998-08-04-SNAP. All upgrades have been both binaries and kernel source, with the kernel recompiled after each time. I'm using NAT to gateway between a campus LAN and my local machines. Natd produces a *lot* of messages saying: natd: Failed to write packet back (host is down) By a lot, I mean hundreds a day. This is, at worst, a minor annoyance. A more serious problem is that a couple times a day natd exits with a signal 11 and dumps core, killing both gatewaying and the machine's own network connectivity until natd is loaded again. It usually seems to do this when there's no traffic being passed; I've never had it go while I had connections active, though this might be coincidence. Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message