Software: Apache/2.2.3 (CentOS). PHP/5.1.6 

uname -a: Linux mx-ll-110-164-51-230.static.3bb.co.th 2.6.18-194.el5PAE #1 SMP Fri Apr 2 15:37:44
EDT 2010 i686 

uid=48(apache) gid=48(apache) groups=48(apache) 

Safe-mode: OFF (not secure)

/usr/share/doc/isdn4k-utils-3.2/   drwxr-xr-x
Free 50.99 GB of 127.8 GB (39.9%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     i4lfaq-11.html (4.3 KB)      -rw-r--r--

11. pap: Authenticate properly (especially with PAP)

11.1 pap_optionauth: When dialing out, I get the message "pppd: peer authentication required but no authentication files accessible." What does this mean?

Most likely the option "auth" was set by mistake. Then the other side is required to be authorized.

11.2 pap_requestauth: I cannot establish a connection - it's rejected by the other side. In the log file I find a message that's something like: "sent (0) (LCP ConfReq id=0x1 mru 1500 auth pap magic 0xcd12e9c4"

Like in the last question, an option has been set that requires the other side to be authorized. These options shouldn't be set. Possible candidates are: "+pap" as well as "+chap".

11.3 pap_rejectauth: I cannot establish a connection - it's rejected by the other side. In the log file I find a message that's something like: "sent (0) (LCP ConfRej id=0x1 auth pap"

Your computer is refusing to identify itself with user name (e.g. XXX) and password (e.g. YYY). That only works with the authorization options "user XXX" and "remotename YYY" for ipppd or pppd together with a correct (!) /etc/ppp/pap-secrets. With a password of ZZZ it should ideally look like this:

XXX YYY ZZZ *

* * ZZZ *

11.4 pap_checkpwd: How can I check which password is actually sent to the remote side?

Use the options debug and +pwlog for ipppd or pppd. Then you can see your password in the log file.

11.5 pap_passwd: I have problems with PAP or CHAP authentication. It does not work although I'm sure I entered passwords etc. correctly.

Stefan A. Muehlenweg Stefan.A.Muehlenweg@samhh.hanse.de wrote on 4 Oct 1996:

I had exactly the same problem/the same error message. The cause for it was that I had three entries in chap-secrets/pap-secrets (for client, server, secret), but not a fourth one (IP addresses). BUT: after the third entry were some BLANKs. After removing the trailing BLANKs and/or TABs (i)pppd is now very satisfied with my auth-files.