On Thu, 21 Oct 1999, Ulrik Buchholtz wrote:
|On Sat, 24 Oct 1999, Clifford Kite wrote:
|> ...
|> the server has either been replaced or "upgraded". Try replacing the pppd
|> option "asyncmap 0" with "asyncmap a0000" .
|
|Didn't help.
Darn!
|But then I tried to "require-pap" instead, and ...
... they won't authenticate to you? That's what require-pap means, that
you require the peer to authenticate itself to you with PAP, not that you
require pppd to use PAP to authenticate yourself to the peer. The
authenticator must approve the authentication method, the authenticatee
can only suggest alternatives by using a Configure-Nak.
[Edited]
|cbcp_lowerup
|want: 14
This is an announcement that the CPCP layer is up and the type of CBCP
that's needed, but I'd have to find and read the RFC to find out what the
type means. It's a debug type of message, a little surprising, but it's
not related to the current problem.
|HOW, I repeat, HOW can pppd say that "peer refused to authenticate" when I
|got a "ConfAck"???????
|And what does "want: 14" mean?
See the previous comments.
|By the way, before the number change, it used chap m$oft, but now they agree
|on chap MD5, howcome???
I can't answer that one except to say they may not have had CHAP configured
as an option before the change.
The CHAP authentication failed because the username or secret isn't what
the peer needs to authenticate you. The "asyncmap a0000" didn't work so,
assuming that you made no change on your host except for the telephone
number, the username or secret in the peer database has been changed, or,
perhaps, the peer database for CHAP is different from the one for MS-CHAP.
I'm not sure it's possible for pppd to Configure-Nak CHAP in order to
suggest MS-CHAP . At least there doesn't seem to be anything concerning
that in the pppd documentation.
BTW on reviewing the original post I found the receive-all option in your
options list. :/
---
Clifford Kite Not a guru. (tm)
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
