Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!sdcsvax!ucbvax!mit-kermit.UUCP!krowitz
From: krowitz@mit-kermit.UUCP.UUCP
Newsgroups: comp.sys.apollo
Subject: Re:  subneting
Message-ID: <8709011605.AA03888@EDDIE.MIT.EDU>
Date: Tue, 1-Sep-87 11:32:42 EDT
Article-I.D.: EDDIE.8709011605.AA03888
Posted: Tue Sep  1 11:32:42 1987
Date-Received: Thu, 3-Sep-87 01:02:31 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 50

we are using the rip_server in stead of routed. The problems ...
the Apollo ring is a subnet of the MIT campus net (net 18.138, 
the main MIT net is net 18). However we are not directly connected
to the main campus net. Instead we are physically connected to
a deparment ethernet which is also a subnet (18.83) of the main
MIT campus net. (ie. the Apollo ring (18.138) is connected to
the deparment ether (18.83) which is then connected to the
main MIT net ). The problems seem to be the following:
1) the BSD4.2 machines on the deparmental ethernet do not seem
   to support subnets (please! correct me if I am mistaken!), so
   they all have the command "route add default ether-to-campus-gateway 1"
   added to the end of their /etc/rc.local file. This means that
   they can all talk to each other on the departmental ethernet
   and that all other packets are routed out to the gateway to 
   the main campus net. There seems to be no way to tell the BSD4.2
   machines to route packets for the Apollos (ie. subnet 18.138)
   through the Apollo gateway unless I give a seperate "route add"
   command for each of the Apollo hosts on each of the BSD4.2
   machines. Perhaps we can get the department-to-campus gateway
   (which understands subnets) to re-route packets for the
   Apollo subnet back to the Apollo gateway ...

2) I have yet to find a way to tell the Apollos to route all
   packets that are not destined for either the Apollo subnet
   or the departmental ethernet to the department-to-campus
   gateway (ie. something similar to the "route add default"
   command). If I'm sitting on one of the BSD4.2 hosts on the
   department's ethernet, I can type "telnet 128.87.2.2" 
   (a host at UCLA) and get connected despite the fact that
   there is *no* routing info in the local hosts /etc/hosts
   or /etc/networks files, only the "route add default"
   command in the /etc/rc.local file which directs the
   packets for all hosts not in the local tables to the
   *very* intelligent department-to-campus gateway. I've
   got a call into Apollo to see if they can figure out
   a way to do this with the AEGIS tcp servers ... I don't
   know ... maybe we'll have to switch over to using the
   DOMAIN/IX servers and use the "route add default"
   command on the Apollos.

3) the rip_server on the Apollo-to-department gateway keeps
   going belly up. I haven't had time to look at this yet.


 -- 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)