From owner-freebsd-security  Fri Jan  7 13:33: 8 2000
Delivered-To: freebsd-security@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP id 8E3DB14E98
	for <freebsd-security@FreeBSD.ORG>; Fri,  7 Jan 2000 13:33:01 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id NAA97841;
	Fri, 7 Jan 2000 13:32:54 -0800 (PST)
	(envelope-from dillon)
Date: Fri, 7 Jan 2000 13:32:54 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <200001072132.NAA97841@apollo.backplane.com>
To: Michael Maxwell <drwho@xnet.com>
Cc: freebsd-security@FreeBSD.ORG
Subject: Re: Sudden crashing?
References:  <20000107152815.A11225@typhoon.xnet.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

:So far, one of my servers, a BSD 3.2-R machine, has mysteriously crashed
:twice this week.  This machine functions as a gateway and firewall to our
:internet connection, so it's the most visible host here.  I use ipfw to
:block pretty much all the low ports except those we really need, such as
:ssh, ntp, smtp, etc...
:
:I don't see anything in the logs indicating what might have happened.
:
:Not only that, but ipfw *refuses* to log to syslog on this box!?!  My 
:/etc/syslog.conf is an exact copy of the same file on another machine
:which DOES correctly log ipfw.
:
:Any ideas?

    The very first thing I would do is upgrade the machine to 3.4-R.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message