Thread View: comp.sys.next.software
2 messages
2 total messages
Started by John R. Cary
Sat, 12 Dec 1992 20:10
Gateway problems with Mamakos SLIP
Author: John R. Cary
Date: Sat, 12 Dec 1992 20:10
Date: Sat, 12 Dec 1992 20:10
52 lines
2539 bytes
2539 bytes
I am trying to set up my NeXT as a slip server using the SLIP package by L. Mamakos. I finally got slip to work for the subnet (128.138.145) on which the NeXT sits, but I cannot communicate with machines not on the 128.138.145 subnet. On the slip server (the NeXT, apaschair) I set ip# = 128.138.145.7 slip0local = 128.138.145.13 slip0remote = 128.138.145.12 slip0netmask = 128.138.255.254 (If this last is .255, 'netstat -r' on the NeXT does not show .12 routed via .13. If this last is .0, it works just as well.) On the Mac I set VersatermAdminSLIP to ip# = 128.138.145.12 netmask = 255.255.255.255 gateway = 128.138.145.13 At this point I was able to telnet successfully to 128.138.145.7. However, I could not log in to 128.138.145.4 (apas). I then went to apas and added the static route to 128.138.145.12 being by the gateway 128.138.145.7. At this point I was able to telnet to 128.138.145.4. I cannot log in to other machines on the subnet. I presume I have to tell each of them what the route to 128.138.145.12 is. I cannot log into any machines off the subnet, and I cannot log into any machines by name. I presume that no machines off the 128.138.145 subnet know how to get to 128.138.145.13. This would explain both the lack of off-subnet telnet and nameservice. Does my Next need to be broadcasting that packets to 128.138.145.12 should be sent to 128.138.145.7? How is this done? Or should my NeXT automatically pick off any packets to 128.138.145.12? Again, how? Or, does the subnet gateway (phys-gw145 = 128.138.145.1) need to be set up so that it knows that packets to 128.138.145.12 are to be sent to 128.138.145.7? Thanks for any help. -- -------------------------- John R. Cary cary@boulder.colorado.edu Department of Astrophysical, Planetary and Atmospheric Sciences University of Colorado, Boulder, CO 80309-0391 ph. (303) 492-1489 fax (303) 492-0642
Re: Gateway problems with Mamakos SLIP
Author: chris Chris Larson
Date: Tue, 15 Dec 1992 17:45
Date: Tue, 15 Dec 1992 17:45
28 lines
1752 bytes
1752 bytes
John R. Cary writes > I am trying to set up my NeXT as a slip server using the SLIP > package by L. Mamakos. > > I cannot log into any machines off the subnet, and I cannot > log into any machines by name. I presume that no machines off the > 128.138.145 subnet know how to get to 128.138.145.13. This would > explain both the lack of off-subnet telnet and nameservice. > The naming problem is a netinfo thing. Even though netinfo probably isn't running on the SLIP client machine, somebody still uses the netinfo database for net name and address lookup. Just add all the appropriate names and net addresses to the netinfo hosts database. We've been playing with the routing problem for awhile now, and almost have it covered. We finally ended up with static routing from each subnet back to the SLIP server. For specifics, I'll need to pass this on to the gurus. There is hope. I can now set up a SLIP connection from my home, and NFS mount remote file systems (that are subnets) on my machine. Chris -- Chris Larson <==> chris@oceania.com <==> NeXT Mail is cool Oceania Health Care Systems Palo Alto, CA The Software Ranch Park City, UT
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads