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!ucbvax!info-vax From: info-vax@ucbvax.ARPA Newsgroups: fa.info-vax Subject: Re: Pinging gateways Message-ID: <2479@ucbvax.ARPA> Date: Thu, 11-Oct-84 14:51:35 EDT Article-I.D.: ucbvax.2479 Posted: Thu Oct 11 14:51:35 1984 Date-Received: Sat, 13-Oct-84 02:01:26 EDT Sender: daemon@ucbvax.ARPA Organization: University of California at Berkeley Lines: 22 From: Rudy.Nedved@CMU-CS-A.ARPA Well. Yesterday CMU-Gateway stop getting routing updates for MILNET from the core gateway that we get information from for about 4 hours. The result was that CMU-CS-A (ARPANET) could not talk to CMU-CS-B (MILNET) but CMU-CS-B could talk to CMU-CS-A. The subtle difference (I believe) is that the TOPS-10 code will use the IMP/port information it keeps on active connection when sending a response....and uses its assigned gateway when it initiates a connection. Given that if you give a packet to a one of your two assigned ARPANET/MILNET gateways...it tends to deliver it even though the core gateways don't tell anyone else about its delivery ability. I don't like the situation and wish there were "fixes" but one must recognize that the "growth" of the Internet structure has been like an explosion...kinda of unexpected....the core gateways and other gateways are having a problem dealing with the information (that is why I like the concept of hiding as much internal network structure as possible from external gateways). -Rudy