Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 8/7/84; site ucbvax.ARPA
Path: utzoo!linus!decvax!decwrl!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: re: pinging and networking
Message-ID: <2633@ucbvax.ARPA>
Date: Wed, 17-Oct-84 18:18:24 EDT
Article-I.D.: ucbvax.2633
Posted: Wed Oct 17 18:18:24 1984
Date-Received: Fri, 19-Oct-84 04:49:48 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 24

From: Provan@LLL-MFE.ARPA

What Rudy is trying to say is that it's very bad to "ping" *regularly*.
He's thinking of some unfriendly behavior that some TOPS-20 sites used
to do.  They used to send packets (as Rudy describes) to every gateway
they knew of every minute or two.  The load on the network was excessive
and everyone got all upset about it.  Since them this behavior has been
stamped out (we hope).

Now that those of you on Info-Vax that aren't on TCP-IP are up-to-date
about what Rudy's so upset about, we can proceed with the discussion.

It sounds like what Ron wants is a one shot program that either runs out
to see if the route to Blat is really valid or see if all routes in some
route table are valid.  There are three possible mechanisms for this that
I can think of off hand.  The best if you want timings is ICMP echo
messages aimed at the host you want to check.  The easiest is to try to
open a Telnet connection (if it fails, the route's probably not right).

Now that we've calmed down the TCP-IP people, is there anything out there
that will do the job?
							don
CC:     Rudy.Nedved@CMU-CS-A.ARPA,
	Info-vax@sri-kl.arpa