On Wed, 30 Dec 1998, Michael Talbot-Wilson wrote:
> AutoPPP is a complication of dubious merit. In a way it's a nice
> idea, but it gives you nothing you can't get by telnetting over the
> PPP link once it's up. On the minus side, it prevents you from
> using CHAP authentication, and that is crucial to support mobile
> phone dial-ins, IMHO.
>
> I would forget AutoPPP. Set up mgetty, verify that you can dial
> in and get a login session, then move on to the PPP problem. For
> that, start by reading the man page.
Are you sure that mgetty AutoPPP doesn't support CHAP? As I understand it
(I've only used PAP), mgetty just looks for the PPP handshaking after it
picks up the line, then fires up pppd with whatever options the AutoPPP
(or options file) specifies. At this point mgetty shouldn't be involved.
IMO, Win95 PPP support is much easier with AutoPPP than setting up a pppd
shell login and a Win95 login script (I did both for a previous dial-in
configuration).
I agree that testing the shell login before proceeding to PPP setup is
important. I've made the same recommendation to others on this list
several times in the past few weeks. Thanks for emphasizing that.
Have a Happy New Year!
Geof
DISCLAIMER: The comments above are my own and may not represent the views
of my employer.
+-------------------------------+-------------------------------------------+
: Geoffrey P. Goodrum : US Department of Commerce :
: +1-301-457-5100 : NOAA/NESDIS National Climatic Data Center :
: [EMAIL PROTECTED]: Satellite Services Branch :
+-------------------------------+-------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
