LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   Can't dial with wvdial (https://www.linuxquestions.org/questions/fedora-35/cant-dial-with-wvdial-198738/)

pen^2 06-28-2004 01:14 PM

Can't dial with wvdial
 
Hi,

I have a default desktop installation of Fedora Core 2, and I'm trying to connect to the internet using wvdial.

(I did all of the following as root)

I type "wvdialconf /etc/wvdial.conf"

And I get the normal output (acording to documentation) except for the end where it says "/etc/wvdial.conf<warn>: Can't read config file /etc/wvdial.conf: No such file or directory"

Then I edit the wvdial.conf file that was created, adding my dial in number, username, and password, and then save it. After that I type "wvdial" and it initialises the modem, but then complaines that I have not entered a valid phone number, username, or password.

Please help, what am I doing wrong?

b0uncer 06-28-2004 02:14 PM

I had to do things like this to avoid the errormessage (as root):

touch /etc/wvdial.conf
wvdialconf /etc/wvdial.conf

then edit the created file, save and

wvdial

and that was it. the touch command makes sure the file is there so the wvdialconf can write to it...try that out :)

pen^2 06-29-2004 12:48 AM

Thank you very much. I can now dial in, but I get disconnected straight away. I guess I have some more googling to do.

Thanks again.

pen^2 06-29-2004 07:19 AM

Ok, yet more problems now. I'm getting so fucking sick of this. I never have trouble with any other distro. Anyway now when I run wvdial I get the following output:

--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT(ISP number)
--> Waiting for carrier.
ATDT(ISP number)
CONNECT 115200
--> Carrier detected. Waiting for prompt.
~[7f]}#@!]!@} &}"}&} }*} } }#}$@#}%}&$[08]*/}'}"}(}"}1}$}%t}3}*}!RKM-POPO}-~
--> PPP negotiation detected.
Starting pppd at Tue Jun 29 13:52:11 2004
--> pid of pppd: 2957
--> Disconnecting at Tue Jun 29 13:52:11 2004
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail
--> Try again and look into /var/log/messages and the wvdial and pppd man

pages for more information.
--> Auto Reconnect will be attempted in 5 seconds

As you can see, it pretty much dials in, and disconnects straight
away, and in the few seconds it seems to be online, I can't send or
recieve anything to or from the internet anyway.

I checked my /var/log/messages file I found the following lines that
might be relevant:

Jun 29 13:38:07 localhost pppd[2783]: pppd 2.4.2 started by root, uid 0
Jun 29 13:38:08 localhost pppd[2783]: Using interface ppp0
Jun 29 13:38:08 localhost pppd[2783]: Connect: ppp0 <--> /dev/ttys1
Jun 29 13:38:08 localhost pppd[2783]: Hangup (SIGHUP)
Jun 29 13:38:26 localhost pppd[2783]: Modem hangup
Jun 29 13:38:26 localhost pppd[2783]: Connection terminated.
Jun 29 13:38:26 localhost pppd[2783]: Exit

Any more help would be very much appreciated.

Thank you.

b0uncer 06-29-2004 07:54 AM

hmm..I assume you have /etc/hosts, /etc/hosts.conf and /etc/resolv.conf set up (though they shouldn't affect this..but anyway, when you get connected they need to be all right)

the error code seems to mean that your modem is fighting back..but I'm not completely sure about that, since I have had similar disconnection-problem myself; after a connection it was up for about 10 seconds (and did nothing) and then died. I was unable to find the cause for the problem back then, but updating wvdial (and pppd too?) did the trick and everything worked fine after that.

I'm not sure whether you use the newest version of wvdial or not..but after some googling it seems that some version(s) of wvdial (ok - let's not say wvdial but either it or it's dependencies) are "broken" so they just don't work. I didn't find an answer that would explain whether it was a bad compilation, "broken" binary or some system-thing that caused this..but anyway, updating wvdial and it's dependencies seemed to fix this problem on the cases I saw while googling..

so, if you can't find any other solution (it can't be rights-based, since you run pppd as root), try updating wvdial and possibly it's dependencies. or, actually updating pppd, since I can't see any error caused by wvdial itself (it connects, after all, and the error is given by pppd)..

pen^2 06-29-2004 08:01 AM

That would make sense. I am typing this from SuSE 9.0 with the same modem, connecting through a differen't version of wvdial. I'll give it a try. Thanks again for all the help.


All times are GMT -5. The time now is 06:03 PM.