Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!weiner From: weiner@novavax.UUCP (Bob Weiner) Newsgroups: comp.sys.apollo Subject: Re: SR10.1 TCP/IP question ... Message-ID: <1214@novavax.UUCP> Date: 21 Apr 89 04:56:52 GMT References: <8904181910.AA07281@richter.mit.edu> Organization: Nova University, Fort Lauderdale, FL Lines: 32 In-reply-to: krowitz@RICHTER.MIT.EDU's message of 18 Apr 89 19:10:22 GMT David Krowitz writes: I've nstalled SR10.1 on my DN560 using the /etc/hosts files (as opposed to name servers). The DN560 is attached to our ringnet which, in turn, is connected to our campus etheret by a DN660 running SR9.7 and Domain TCP 3.1 (the AEGIS TCP/IP). Yet when the machine is booted, we can not connect to any machine (ie. ping, telet or ftp) not on the local ringnet *unless* the rip_server (the AEGIS TCP/IP routing daemon) was running on the gateway at the time the sr10 node was booted. The /etc/hosts file lists both an address on the Apollo ringnet and the campus ethernet for the gateway node, and the subnet mask should have been defined correctly by the 'ifconfig' command, yet we can not access the campus ethernet unless the routing daemon was running on the sr9.7 machine which is the gateway. We've had this same problem except that our Ethernet gateway node along with all of our other nodes is running SR10.1 (BSD). I finally found an Apollo tech rep in Texas who knew about this and said that yes, none of the routing on the non-gateway nodes will work after the gateway node is taken down and then rebooted. He said we would need a script that checked every so often if the gateway had gone down and then executed /etc/routed -f -h on all of the other nodes again. This is definitely a pain that Apollo should fix. We want dynamic routing to be fully dynamic. Any tech help from the sharp Apollo R&D minds that read this list would be greatly appreciated. -- Bob Weiner, Motorola, Inc., USENET: ...!gatech!uflorida!novavax!weiner (407) 738-2087