Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!LANL.GOV!cpw%sneezy
From: cpw%sneezy@LANL.GOV (C. Philip Wood)
Newsgroups: comp.protocols.tcp-ip
Subject: Broadcast Storms
Message-ID: <8708261820.AA16452@sneezy.lanl.gov>
Date: Wed, 26-Aug-87 14:20:28 EDT
Article-I.D.: sneezy.8708261820.AA16452
Posted: Wed Aug 26 14:20:28 1987
Date-Received: Fri, 28-Aug-87 06:19:09 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17

This subject may have been discussed before.  But,
LANL was experiencing broadcast storms on an ethernet.
About 100 hosts on the ether would send a message back to
a lone Ultrix V2.0-1  (Microvax) system running the rwho daemon 
every few minutes.  It was broadcasting to 128.165.255.255 and all
these hosts were sending back some kind of arp to find out who the
guy was so they could probably send him some kind of response
(Connection refused?).

Anyhow, as in the problem with reverse arp responses of zero (a previous
missive) I spent some time tracking down the culprit.  Once I found
him, the fix was to terminate the rwho daemon (and remove entry from
the startup file).

Network management in a heterogeneous environment, anyone?

Phil Wood  (cpw@lanl.gov