PPP: Authentication failure
Hallo! I configured my modem and PPP through YaST and wvdial.conf in Suse 7.3 on my Powerbook Firewire. What I haven't been able to solve so far is an authentication dialog failure between the modem and the provider (my university). University modem pool support could only confirm my settings but otherwise does not support Linux. Thus, maybe somebody here would have an idea what I am still missing to get the modem running. I tried to take over the settings from my MacOS partition for which the modem is connecting fine. Those are: Remote Access: registered user, username, password, phone number Options: redial off, allow error correction and compression in modem, use TCP header compression Modem: 56k, sound on, dialing tone, do not ignore dialing tone TCP/IP: Connect via PPP, Configure: using PPP server (there is a nameserver IP, but university support said that that is bogus) In linux the provider part in wvdial.conf looks like this: [Dialer UofC] Ask Password = 0 Auto DNS = 1 Auto Reconnect = 0 DNS1 = DNS2 = Demand = no Idle Seconds = 180 Inherits = Dialer modem0 Password = [password] Phone = [number] Provider = UofCModem Username =[username] YaST2 Record = provider I am connecting using Kinternet and the log gives me the following messages: ... Entering PPP mode Async interface address is unnumbered (Loop back 1) Your IP address [number]. MTU is 1500 bytes Header compression will match your system. -> Looks like a welcome message -> Starting pppd at [date] -> pid of pppd: 7356 -> PPP was killed (signal 11) -> Disconnecting We are disconnected. -> PPP daemon has died. Peer didn't authenticate itself (exit code 11). Any ideas? Thanks! Jutta
On Thu, Feb 28, Jutta Buschbom wrote:
I configured my modem and PPP through YaST and wvdial.conf in Suse 7.3 on my Powerbook Firewire. What I haven't been able to solve so far is an authentication dialog failure between the modem and the provider (my university). University modem pool support could only confirm my settings but otherwise does not support Linux. Thus, maybe somebody here would have an idea what I am still missing to get the modem running.
I tried to take over the settings from my MacOS partition for which the modem is connecting fine. Those are: Remote Access: registered user, username, password, phone number Options: redial off, allow error correction and compression in modem, use TCP header compression Modem: 56k, sound on, dialing tone, do not ignore dialing tone TCP/IP: Connect via PPP, Configure: using PPP server (there is a nameserver IP, but university support said that that is bogus)
In linux the provider part in wvdial.conf looks like this: [Dialer UofC] Ask Password = 0 Auto DNS = 1 Auto Reconnect = 0 DNS1 = DNS2 = Demand = no Idle Seconds = 180 Inherits = Dialer modem0 Password = [password] Phone = [number] Provider = UofCModem Username =[username] YaST2 Record = provider
Do you have "Stupid Mode = 1" in your wvdial.conf? I think that was missing in 7.3 and may help.
I am connecting using Kinternet and the log gives me the following messages: ... Entering PPP mode Async interface address is unnumbered (Loop back 1) Your IP address [number]. MTU is 1500 bytes Header compression will match your system. -> Looks like a welcome message -> Starting pppd at [date] -> pid of pppd: 7356 -> PPP was killed (signal 11) -> Disconnecting We are disconnected. -> PPP daemon has died. Peer didn't authenticate itself (exit code 11).
Any ideas? Thanks!
Jutta
Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Hi Olaf,
Do you have "Stupid Mode = 1" in your wvdial.conf? I think that was missing in 7.3 and may help.
Inserted it into [Dialer <provider>} and [Dialer default] of wvdial.conf. Unfortunately, that's not it. Kinternet's log now gives me this error message: .... ATDT <number> Connect 115200 -> Carrier detected. Starting PPP immediately -> Starting ppd at <date> -> pid of ppd: <number> -> PPP was killed! (signal 11) -> Diconnecting .... I then went into /etc/ppp/options to see if noauth is active. It is. The active options for PPP are: debug, noauth, crtscts, lock, modem, asyncmap0, nodetach, lcp-echo-intervall 30, lcp-echo-failure 4, lcp-max-configure 60, lcp-restart2, idle 600, noipx. In /etc/ppp/peers/wvdial I find: noauth, name wvdial, debug, defaultroute, replacedefaultroute. Any idea? Jutta
Hi,
Do you have "Stupid Mode = 1" in your wvdial.conf? I think that was missing in 7.3 and may help.
Inserted it into [Dialer <provider>} and [Dialer default] of wvdial.conf. Unfortunately, that's not it. Kinternet's log now gives me this error message: .... ATDT <number> Connect 115200 -> Carrier detected. Starting PPP immediately -> Starting ppd at <date> -> pid of ppd: <number> -> PPP was killed! (signal 11) -> Diconnecting ....
There was a bug in the original 7.3 passwordfd pppd plugin. SuSE has provided an update a while ago. Maybe your problem is related to this. Uwe
Hallo Uwe,
There was a bug in the original 7.3 passwordfd pppd plugin. SuSE has provided an update a while ago. Maybe your problem is related to this.
Sometimes I did get the an error relating to the passwordfd plugin - always correlated with having a green circle behind kinternets symbol in the menu. Don't know how I got there. Right now the passwordfd does not seem to be the problem, at least I don't get any messages relating to it. I nevertheless checked which version of ppp is installed on my system and it seems to be the right one: rpm -q -i ppp_ssl gives a not installed message rpm -q -i ppp gives: version 2.4.1, release 28, build Ho Suse support database in one article says that the password should be in all three of these files: /etc/wvdial.conf (username and password are in there alright) /etc/ppp/pap-secrets (it is not in there) /etc/ppp/chap-secrets (it is not in there) I thought that if the password is in wvdial.conf that it then would automatically be passed on to the authorization process? But maybe not? I can't check what is happening if I enter the password in these files, but will try later, since this is the only thing I can think of right now. Jutta
On Thu, Mar 07, Jutta Buschbom wrote:
Hallo Uwe,
There was a bug in the original 7.3 passwordfd pppd plugin. SuSE has provided an update a while ago. Maybe your problem is related to this.
Sometimes I did get the an error relating to the passwordfd plugin - always correlated with having a green circle behind kinternets symbol in the menu. Don't know how I got there. Right now the passwordfd does not seem to be the problem, at least I don't get any messages relating to it. I nevertheless checked which version of ppp is installed on my system and it seems to be the right one: rpm -q -i ppp_ssl gives a not installed message rpm -q -i ppp gives: version 2.4.1, release 28, build Ho
Suse support database in one article says that the password should be in all three of these files: /etc/wvdial.conf (username and password are in there alright) /etc/ppp/pap-secrets (it is not in there) /etc/ppp/chap-secrets (it is not in there) I thought that if the password is in wvdial.conf that it then would automatically be passed on to the authorization process? But maybe not? I can't check what is happening if I enter the password in these files, but will try later, since this is the only thing I can think of right now.
Does your dialin require PAP or CHAP for authentication? Did you try wvdial.lxdialog to configure wvdial? Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
participants (3)
-
Jutta Buschbom -
Olaf Hering -
Uwe Hees