From owner-freebsd-current  Mon Jul  3 05:03:18 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id FAA02609
          for current-outgoing; Mon, 3 Jul 1995 05:03:18 -0700
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA02601
          for <current@freebsd.org>; Mon, 3 Jul 1995 05:03:10 -0700
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD4.4)
	id WAA18182; Mon, 3 Jul 1995 22:01:37 +1000
From: michael butler <imb@scgt.oz.au>
Message-Id: <199507031201.WAA18182@asstdc.scgt.oz.au>
Subject: Re: spontaneous reboots ?
To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes)
Date: Mon, 3 Jul 1995 22:01:36 +1000 (EST)
Cc: current@freebsd.org
In-Reply-To: <199507031002.DAA18112@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jul 3, 95 03:02:02 am
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 375       
Sender: current-owner@freebsd.org
Precedence: bulk

Rodney W. Grimes writes:

> Not really, have tcpdump filter on the MAC address of the problem machine.

It's in the ipfw code .. the packet that causes the panic is addressed to a
machine which is inaccessible by virtue of an "ipfw policy deny". I don't
see it from the other machinery on this ether because they're "secure" and
permitted to traverse that gateway,

	michael