Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!bionet!agate!ucbvax!asylum.sf.ca.us!romkey
From: romkey@asylum.sf.ca.us (John Romkey)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Broadcasting - possible abuse?
Message-ID: <8909072203.AA24058@asylum.sf.ca.us>
Date: 8 Sep 89 05:03:50 GMT
References: <8909072316.AA13106@ti.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: romkey@asylum.sf.ca.us
Organization: The Internet
Lines: 7

It's probably an system running an old Berkeley UNIX TCP that's
getting packets sent to the IP broadcast address but not recognizing
them as such and then, thinking it's a router, trying to forward them,
finding their for its same subnet, and ARP'ing for them. One solution
is to make sure that all your systems running Berkeley have the
variable ipforwarding in the kernel set to 0 to disable routing.
				- john