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!watmath!clyde!burl!ulysses!cbosgd!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: Routes, pinging, ad infinitum...
Message-ID: <2712@ucbvax.ARPA>
Date: Fri, 19-Oct-84 17:41:38 EDT
Article-I.D.: ucbvax.2712
Posted: Fri Oct 19 17:41:38 1984
Date-Received: Sun, 21-Oct-84 13:31:08 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 52

From: Dennis Rockwell 

	From: Ron Tencati 
	Subject: Routes, pinging, ad infinitum...
	Date: 18 Oct 1984 1624 PDT

	
	Dennis,

		Paul Milazzo contacted me yesterday and helped me get
	my routes straightto RICE. I can now send to RICE and IAP,
	which means both of those networks are now "reachable". I
	usually don't know who I can't get to until one of my users
	sends netmail to somewhere, and I notice that the mail just
	sits there for 4 or 5 days.  The current problem seems to be
	host bbn-labs-b.arpa. I can't open a connection on either
	8.7.0.2 or 128.11.1.2. What I get are time-outs.

bbn-labs-b has been playing yo-yo lately, but it's usually up and running.
What are your routings to net 8 and net 128.11?  net 8 is reachable through
BBN-NET-GW (10.4.0.82), and 128.11 through bbn-cronus-gw (10.6.0.82).  If
that fails, try redirecting the mail to bbn-unix (10.0.0.82), which will
hold the mail for forwarding.  Hmm... are you having trouble getting to IMP
82?  Try some other hosts on those nets to check the routing.

		The software we run is the Kashtan/4.1cBSD package
	under VMS.  We got itabout 2 years ago.  Dave has been helpful
	in getting us software that updates our host tables.  I update
	to a new table as soon as I get the message from NIC.

Good practice.  I've been thinking of a special MMDF "rcvtrip" analogue that
catches the "new host table" messages and automagically grabs the host
table and do the munging.  Dreams....

		As I mentioned previously, the errors we see are
	"network unreachable", or "connection timed out" while trying
	to send mail (Telnet and FTP do it also).Thank you for your
	information and offer to help.  Slowly but surely, things are
	looking up.

Generally, "unreachable" means your routing tables are messed up (or a
gateway is out), and timeouts mean the packets are misdirected somehow.
Lots of nets (essentially everything except an 1822 net) will not complain
if packets are sent to bogus addresses.

	Ron
	------

Good luck!

Dennis Rockwell
CSNET Technical Staff