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: <2629@ucbvax.ARPA> Date: Wed, 17-Oct-84 17:32:59 EDT Article-I.D.: ucbvax.2629 Posted: Wed Oct 17 17:32:59 1984 Date-Received: Fri, 19-Oct-84 04:49:16 EDT Sender: daemon@ucbvax.ARPA Organization: University of California at Berkeley Lines: 36 From: Rudy.Nedved@CMU-CS-A.ARPA don, You seemed to have missed several points in my message. Ron I assume is trying to "fix problems" with JPL-VLSI and other hosts. Either the hosts that he wants to talk to are ARPANET hosts or they are behind gateways. If the gateways are not routing correctly then they have to be fixed. If he has a lengthy routing table and does not use one or two well known gateways then he is going to have problems everytime the network configuration changes...I assume his system has ICMP implemented and that it interacts with his routing code. ======== The most important point is everyone is seeing the problems with the gateways at the moment and the BBN folks are working on the systems. I don't enjoy the fact that CMU-CS-A can't get to CMU-CS-B because the EGP gateway we are using dropped MILNET. People are working on it and no amount of pinging and testing is going to make things better for a host. The only short cut is to find find out what gateways are between you and the host you want to talk to and put the first one in the path in your table for that host. If that gateway goes down, your stcuck. If the network behind that gateway changes, your stuck. If someone badly needs network service then make your host multiaddressed and get a second connection to that network and avoid other people's gateways. -Rudy