🚀 go-pugleaf

I am trying to set up my NeXT as a slip server using the SLIP
package by L. Mamakos.  

I got slip to work with static routing 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.0
(If this last is .255, 'netstat -r' on the NeXT does not show .12 routed
via .13.  If this last is .254, it works just as well.)

For this configuration, netstat on the server gives:
apaschair.cary> netstat -r
Routing tables
Destination      Gateway            Flags     Refs     Use  Interface
localhost        localhost          UH          2      713  lo0
apasroad.Colorad apasslip.Colorado. UH          0      152  slip0
apasslip.Colorad localhost          UH          0        0  lo0
default          phys-gw145.Colorad UG          2     6241  en0
128.138.145      apaschair.Colorado U          40    35405  en0
apaschair.cary> netstat -i -n
Name  Mtu   Network     Address            Ipkts Ierrs    Opkts Oerrs  Coll
en0   1500  128.138.145 128.138.145.7      44538     0    38958     0     0
lo0   1536  127         127.0.0.1           3374     0     3374     0     0
etlk0 622   none        none                   0     0        9     0     0
slip0 1006  128.138.145 128.138.145.13       204     0      152     0     0
slip1 1006  none        none                   0     0        0     0     0
en0   1500  none        none               44674     0    38977     0     0

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