Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!caen!sol.ctr.columbia.edu!emory!hubcap!ncrcae!ncr-sd!se-sd!cns!dltaylor
From: dltaylor@cns.SanDiego.NCR.COM (Dan Taylor)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: AmigaNOS to a gateway. Gateway wont let me connect further.
Keywords: Amiga wont route to outside world.! AmigaNOS AmiagKIT26 etc.
Message-ID: <935@cns.SanDiego.NCR.COM>
Date: 6 May 91 21:31:07 GMT
References: <172@dogmelb.dog.oz.au>
Organization: NCR Corp. SE-San Diego
Lines: 17

In <172@dogmelb.dog.oz.au> david@dogmelb.dog.oz.au (David Le Blanc) writes:


>route add host <amiga ip address> <sun3's address> 1

This is EXACTLY what you start with.  The other systems have to know
which gateway, which is what the SLIP-attached Sun3 is, will connect
them to the Amiga.  I remember "routed" being supported on Sun 3s.
Try telling your route server where the Amiga is.  There is a configuration
file for that.  Then the other machines can ask it.

If you are going to run a lot of point-to-point links, you might use
sub-netting, too.  Then you can use:

	route add net <netname> <sun 3>

Dan Taylor