wvdial: The authentication fails with providers who do not permit PAP

Support knowledgebase (hoe_wvdial_planet)
Applies to

SuSE Linux: Version 7.0
This article refers to an older version of SuSE Linux. Therefore some of the informations given in this article may be outdated or the article may contain stale links.

wvdial: Version 1.41

Symptom:

Using wvdial, you want to establish a dial-up connection with a provider who only permits the CHAP authentication procedure

You receive a message saying that the authentication failed, even when making an attempt with the root identity

In the file /var/log/messages you find lines like

Aug 1 08:22:00 erde pppd[999]: rcvd [LCP ConfReq id=0x1    ]
Aug 1 08:22:00 erde pppd[999]: sent [LCP ConfNak id=0x1 ]

Cause:

In earlier versions wvdial deposited the login name and the password in the files /etc/ppp/pap-secrets and /etc/ppp/chap-secrets.

However, in the present release the password is communicated to the pppd with the passwdfd mechanism without any detours, thereby saving one memory step.
The advantage of this is that a provider does not need to be called up with the root identity initially.

Presently this mechanism only works with the authentication procedure PAP.
In case the provider does not support PAP, the authentication will fail.

Solution:

Since an entry in /etc/ppp/chap-secrets has priority over the passwdfd feature, it is sufficient to enter the login name and the password in the file /etc/ppp/chap-secrets manually.

The following format is to be used:

"user name"	*	"password"
For example:
"arcor"		*	"internet"
(use the tab key to separate elements)
Keywords: PAP, CHAP, WVDIAL, PLANET, INTERKOM, AUTHENTICATION

Categories: Network

SDB-hoe_wvdial_planet, Copyright SuSE Linux AG, Nürnberg, Germany - Version: 05. Sep 2000
SuSE Linux AG - Last generated: 16. Okt 2000 by hoelcker (sdb_gen 1.40.0)