Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!ut-sally!husc6!rutgers!ucla-cs!zen!ucbvax!UDEL.EDU!Mills
From: Mills@UDEL.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  No echo from the NIC
Message-ID: <8708052356.aa15855@Huey.UDEL.EDU>
Date: Wed, 5-Aug-87 23:56:57 EDT
Article-I.D.: Huey.8708052356.aa15855
Posted: Wed Aug  5 23:56:57 1987
Date-Received: Sat, 8-Aug-87 08:36:36 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 12

Bob,

I can't believe this. Nobody (!?) pings the NIC unless they can't connect
and wants to find out why not. So the NIC turns off ICMP as a defense
measure? My prior experience has been that ICMP worked, but TCP connections
took a v e r y long time to complete. It is certainly obvious that the
NIC is overloaded; however, if a significant contributory factor is ICMP
echoes, I submit turning them off will only result in their replacement
by TCP connection attempts. Considering the TOPS-20 initial-connection
TCP design, this would be an even worse disaster.

Dave