Xref: utzoo comp.protocols.tcp-ip:16108 alt.sys.sun:3883
Newsgroups: comp.protocols.tcp-ip,alt.sys.sun,osu.sys.sun.managers
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mstar!mstar.morningstar.com!bob
From: bob@MorningStar.Com (Bob Sutterfield)
Subject: Re: SLIP authenication routines & SLIP routing
In-Reply-To: eric@picard.sbi.com.ogi.edu's message of 15 May 91 14:42:38 GMT
Message-ID: <BOB.91May15172657@volitans.MorningStar.Com>
Sender: usenet@MorningStar.COM (USENET Administrator)
Reply-To: bob@MorningStar.Com (Bob Sutterfield)
Organization: Morning Star Technologies
References: <ERIC.91May15104238@picard.sbi.com>
Date: Wed, 15 May 91 21:27:09 GMT
Lines: 16

In article <ERIC.91May15104238@picard.sbi.com> eric@picard.sbi.com.ogi.edu writes:
   Are there authentication utilities of some sort that will be part
   of the SLIP distribution (wherever they're) so that no random site
   can SLIP into one's local network ?  Dial-back modems are really
   not good enough though.
   
That's something that SLIP didn't provide, but has been addressed in
PPP's simple Password Authentication Protocol.  If you're stuck with
SLIP then you'll need to roll your own solution for each case.  Such
arrangements are typically based on login name, system password, etc.

   Also, I want to know how IP packets are routed once they got to the
   remote site.

That's the task of the host IP implementation.  Neither SLIP nor PPP
know anything about routing.