Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!uunet!ncis.tis.llnl.gov!lance.tis.llnl.gov!guerra
From: guerra@lance.tis.llnl.gov (Frank Guerra)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: sliplogin, NCSA telnet, ka9q
Message-ID: <977@ncis.tis.llnl.gov>
Date: 15 Aug 90 23:54:20 GMT
Sender: news@ncis.tis.llnl.gov
Distribution: na
Organization: University of California, Berkeley
Lines: 14

I have a Sun runing sliplogin connected via SLIP to a PC running the ka9q 
package.  The PC also has an ethernet board.  I've connected a second PC
to the first PC with and ethernet cable.  The problem that I'm having has
to do with the routing from the Sun to the second PC.  The Sun knows about 
the first PC by the running of sliplogin which places and entry into the
routing table.  I've tried adding a route for the second PC that routes to the
first PC, but that didn't seem to work to well (at all is more like it).  A
second instantiation of sliplogin with the IP address of the second PC 
succeeded only in confusing the Sun that it stopped using the SLIP connection.
I don't think that gated is necessary for this, but then again it may be the
only course of action.  Is there another approach that I can try?

Frank
guerra@lance.tis.llnl.gov