On Wed, 10 May 2000, Marc Dufresne wrote:

|Redhat 6.1 Intel
|Kernel 2.2.14
|ppp-2.3.10
|
|Using ppp-on scripts and sometimes more frequent than others I cannot 
|connect. My ppplog file indicates [CHAP MD5] peer refused to authenticate, 
|link terminated.
|
|In my options file I have placed the following;
|
|require-pap
|refuse-chap
|
|Still doesn't work. Always says [CHAP MD5] peer refused to authenticate, 
|terminating link.

Heh.  The require-pap option means that you require the peer to
authenticate itself to you, and if the peer is an ISP host then the
probability of that is exceedingly small. 

The refuse-chap option means that you will refuse to authenticate to the
peer with CHAP.  From your description (exact copies of debug logs are
preferred) the peers usually ask for you to authenticate with CHAP, and
they may not have PAP configured as a fall-back option.  Pppd cannot force
the ISP to use PAP to authenticate you, the authentication is always
negotiated and either side can refuse any authentication requested by the
other side.

|After about 7 reconnects, it finally connects and all is well. At first I 
|thought it was diald, but it turns out to be pppd and authentification.

A completed and working PPP connection should not be possible with the
pppd require-pap option present. ???

---
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]

Reply via email to