david@dogmelb.dog.oz.au (David Le Blanc) (05/03/91)
I have used AmigaNOS for a while, and although I can connect to the
machine I am 'slip'ped to, I am CERTAIN that, given routing, I should
not only be able to talk to other machine that the host is networked
with, BUT I should also be able to talk with machine OUTSIDE of the
gateway.
Currently, there is a sun3, running slip through a 9600baud modem to
the outside world.
The same sun3, runs another slip port to my amiga.
The same sun3 is on an 'ether'net with 8 other machine.
The sun3 can talk to the outside world, to local network and to the
amiga, but NOBODY ELSE can talk to the amiga, and the amiga can talk
to only the sun3, and nothing else, whether on the network nor
outside world.
I have at one stage accidently made it so the amiga could talk to one
other machine by executing
route add host <amiga ip address> <sun3's address> 1
on the other machine (on the ethernet, not the outside world).
That confuses me, since to make the amiga talk to that machine I would
have though I needed to TELL THE AMIGA about the other machine,
not tell the other about the amiga! (I'd hate to have to tell ALL
machines about my amiga! That is what routing is for!!)
All I can think of is doing a
route add default <sun3's address> 1
on the amiga side, but that only lets me access the sun3, and I have
had no other bright ideas that actually gave results!
Any help at all would be appreciated!
Thanks
David.
Email: david@dogmelb.dog@munnari.oz | Division of Geomechanics,
TEL. (03) 881 1355 | CSIRO, P.O. Box 54
FAX (03) 881 2052 | Mt Waverley 3149, AUSTRALIA.
"Since these are children's toys, the fire will spread very quickly! So stay
well clear, and be careful not to breath the toxic fumes." -Krusty Gets Busted.32KKG6I@CMUVM.BITNET (Jim Getzinger) (05/04/91)
I've found this problem as well. Your solution is to either do as you mentioned, telling all the other machines about your Amiga, or to ask your system administrator to find the program 'gated'. This program will correctly announce your SLIP connection to the "world" in this case, your other Suns. Routed does not correctly handle point to point connections, but gated does. After starting gated, get on one of the other Suns and type 'netstat -r'. Your amiga should show up in the listings with your gateway correctly. I know this is brief, but if you need more help, drop me a line and I'll try to make it more specific. Good luck! Jim. ======================================================================== Jim Getzinger |"Dammit Jim! We're PROGRAMMERS, not MAGICIANS!" G.A & Sys-admin | Graduate Assistants: 32KKG6I@CMUVM.BITNET | "The few... the proud... the underpaid." ========================================================================
dltaylor@cns.SanDiego.NCR.COM (Dan Taylor) (05/07/91)
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