From owner-freebsd-current  Tue Apr 22 01:05:50 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA00927
          for current-outgoing; Tue, 22 Apr 1997 01:05:50 -0700 (PDT)
Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00922
          for <current@FreeBSD.ORG>; Tue, 22 Apr 1997 01:05:46 -0700 (PDT)
Received: (from bsdcur@localhost)
          by shadows.aeon.net (8.8.5/8.8.3) id LAA15189;
          Tue, 22 Apr 1997 11:03:57 +0300 (EET DST)
From: mika ruohotie <bsdcur@shadows.aeon.net>
Message-Id: <199704220803.LAA15189@shadows.aeon.net>
Subject: Re: dup and other anomalities...
In-Reply-To: <199704212255.PAA07938@root.com> from David Greenman at "Apr 21, 97 03:55:02 pm"
To: dg@root.com
Date: Tue, 22 Apr 1997 11:03:57 +0300 (EET DST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> >my friend has weird problem in his net, check these pings (this is /27),
> >the problem introduced himself after he upgraded from 2.1.5 to 2.2.-stable
> >with make world. before in 2.1.5 no probs.
>    All of those are due to you pinging the broadcast address of the subnet.
> Looks perfectly normal to me.

you mean that the broadcast is supposed to show that cycle alike pingtimes?

why did he start getting those ipfw messages after upgrade?

> David Greenman


mickey