Ran into this quoting change problem too. It affects authname, authkey, and
phone
strings as well. Phone numbers with '*' sequences failed for me, as well my
authname and authkey settings (which contained non-alphanumerics). Encasing
these strings in "" worked for me.
Since your ISP is asking for PAP, I would do the following:
set login
set authname "yourLoginName"
set authkey "yourPassword"
If the empty 'set login' fails to work for you, try
set login "ABORT NO\\sCARRIER TIMEOUT 5 ogin:--ogin: \\U word: \\P"
Maybe somebody can make this new qouting behavior more clear in an example
in the sample ppp.conf installed in /etc? Just so other new users of 4.0
won't get
bitten by the same thing.
> -----Original Message-----
> From: Thomas Dean [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, February 16, 2000 10:00 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Problems with Recent PPP Changes
>
> Thanks for the reply.
>
> > Date: Wed, 16 Feb 2000 01:16:25 -0700
> > From: Warner Losh <[EMAIL PROTECTED]>
> >
> > In message <[EMAIL PROTECTED]> Thomas Dean writes:
> > : What change to ppp did I miss?
> >
> > There were some quoting and comment recognition changes at one
> > point...
> >
>
> That is the problem. My ISP requires a '#' as a leading delimiter for
> the login name. ppp determines the '#' is the start of a line-end
> comment. From the log:
>
> Phase: bundle: Authenticate
> Phase: deflink: his = PAP, mine = none
> Phase: Pap Output: ********
> Warning: Sending empty PAP authname!
> Phase: Pap Input: FAILURE (Invalid Login)
> Phase: deflink: Disconnected!
> Phase: deflink: lcp -> logout
>
> How do I handle the required leading '#' on the login name? Escaping
> it doesn't work.
>
> tomdean
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
