Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!att!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) Newsgroups: comp.sys.apollo Subject: re: Ethernet Message-ID: <9102201742.AA06905@pan.ssec.honeywell.com> Date: 20 Feb 91 17:42:22 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 47 > <> > Some further questions to those with experience in these matters... > > DN3000+ATR+SR10.2 - Can one "simply" plug in a 505 and use it (with the > necessary editing & network setup) in addition to the ATR. Yes. Check the /systest/ssr_util/jumper program. (I just did). Although it references 2 different ATbus ethernet cards, I saw no differences in the jumper settings themselves (what the jumpers selected, but....) > Does one need any additional software, or is there any additional software > that one should be aware of (another ftpd?)? You will need to tell Domain (DDS) services that there is another controller, and what the netIDs are. All machines on a single physical network should have the same network ID, unless you like confusion. Different networks should NOT have the same netID, unless you like things to not work. In the /etc/rc file, you can set up the 'rtsvc' commands as you like. If you are making your DN3000 act as a router, use the "rtsvc -dev DEVICE -net NETID -route" command. If you just want the DN3000 to have access to 2 networks, use the '-noroute' option instead. If you aren't using the controller for DDS services, you don't need to worry too much -- TCP/IP is independent. Other nodes shouldn't need to have anything done (except for maybe changing the netID). You can check DDS routing with the 'lcnet' command. To set up TCP routing you'll need a separate TCP network/subnetwork. Without knowing specifics (are you subnetting; do you have official net numbers; ...) I can't help much there. The extra commands you need are an additional 'ifconfig' invocation (see /etc/rc.local), and either a 'routed' or static- route ('route') entry (or both). Your other nodes on the ring will need to have a route entered to get TCP/IP off the ring, either by using /etc/route to enter a static one (e.g. '/etc/route -f add default dn3000.name 1') or by running /etc/routed on the gateway and on the other nodes ('/etc/routed -f -q'). Running lots of routed processes has its problems -- they tend to crash&burn. This is true even in vanilla Unix. Listening for routes to all over when you know that you're going to push everything through one bottleneck is kinda silly, too. > Is it worthwhile reading "Managing Domain Routing" or others? It's always worthwhile to read the manuals... after you solve the problem. :-) -- jt -- John Thompson Honeywell, SSEC Plymouth, MN 55441 thompson@pan.ssec.honeywell.com Me? Represent Honeywell? You've GOT to be kidding!!!