Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!tcp-ip
From: Geoff@SRI-CSL.ARPA (the tty of Geoffrey S. Goodfellow)
Newsgroups: mod.protocols.tcp-ip
Subject: C/70's ICMP considered anti-social?
Message-ID: <[SRI-CSL.ARPA]29-Nov-85.16:06:58.GEOFF>
Date: Fri, 29-Nov-85 19:06:00 EST
Article-I.D.: <[SRI-CSL.ARPA]29-Nov-85.16:06:58.GEOFF>
Posted: Fri Nov 29 19:06:00 1985
Date-Received: Fri, 29-Nov-85 22:30:21 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 22
Approved: tcp-ip@sri-nic.arpa

Having recently rehomed our system to a local Ethernet, behind a
LSI-11/23 gateway running the BBN software, i've made notice of
strange behavior on the part of BBN C/70 hosts.

It seems that whenever a host on our local net (192.12.33) opens
up a connection to a C/70 host on the ARPANET, the C/70 starts
sending a never ending stream of ICMP messages to us ever 4
seconds -- these messages never stop -- even after we close the
connection.  Currently, our gateway is being bombarded by four
such systems every 4 seconds.

This behavior seems undesirable at best.  Can anyone explain it?
What purpose it serve?  What would one need to know from our
gateway at the frequency of every 4 seconds?  Is their a method
to issue a cease and desist order to the originating host?

This would seem a great hog of IMP and gateway resources,
inter-IMP trunk bandwidth, and in a worst case scenario, a tad
bit expen$ive if ones gateway were on the other side of a Value
Added Network.

g