Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!labrea!jade!ucbvax!mit-richter.UUCP!krowitz
From: krowitz@mit-richter.UUCP (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  TCP problem
Message-ID: <8709111608.AA00163@EDDIE.MIT.EDU>
Date: Fri, 11-Sep-87 11:46:01 EDT
Article-I.D.: EDDIE.8709111608.AA00163
Posted: Fri Sep 11 11:46:01 1987
Date-Received: Sat, 12-Sep-87 19:16:37 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27

I have seen the error message "destination timed out" before
here at MIT. The problem in the past seemed to be a problem
with the routing tables on the ethernet host getting flushed
periodically (probably because it hadn't seen any info [or any
correct info] from the rip servers on the Apollos). What would
happen is that the non-gateway Apollos would know to route
the packets for the ethernet host via the Apollo gateway, but
the ethernet host would lose the routing table that told it
to reply to the non-gateway Apollos via the Apollo gateway.
The ethernet host can always talk to the Apollo gateway 
because it is on the same network -- no routing info is
needed. We solved this problem on our BSD 4.2 machines by
forcing a static entry for the Apollo network into the
routing tables of the ethernet hosts by using the command
"route add apollo-net apollo-gw 1" in the machine's startup
file (/etc/rc.local) Unlike the info provided by the
rip server/routed programs, this entry does not get flushed
if the ethernet host doesn't here any routing info from the
Apollo gateway periodically.


 -- David Krowitz

mit-erl!mit-kermit!krowitz@eddie.mit.edu
mit-erl!mit-kermit!krowitz@mit-eddie.arpa
krowitz@mit-mc.arpa
(in order of decreasing preference)