LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Unable to establish a connection to my ISP? (http://www.linuxquestions.org/questions/linux-networking-3/unable-to-establish-a-connection-to-my-isp-33432/)

phobos 10-22-2002 05:31 AM

Unable to establish a connection to my ISP?
 
Hi,

At the weekend I upgraded to Red Hat 8.0, having previously used Mandrake 8.2 (my first distro). Shortly after getting around to using linux, I ran in to problems with getting drivers for my Winmodem (as you do). Eventually I tracked them down, and got everything to work (under mandrake). I then used wvdial to establish a connection, and everything worked fine. I had to chmod a few files so normal users could connect, but after that everything was fine.

Now that I've upgraded I was able to get drivers for Red hat 8.0 (kernel: 2-4.18-14). My modem is a Conexant HCF 56k PCI (winmodem). My problem now is that any time I'm logged in as a normal user, my modem returns a resource busy message to WvDial during Init. If I'm logged in as root, this problem does not occur.

So while logged in as root, I get to init the modem, and dial my ISP. When it get's to the stage where the connection is authenticated, WvDial goes in to a frenzy of sending the username/password pair, and doesn't seem to establish the connection. This results in it hanging up the modem, and redialing all over again.
PHP Code:

--> WvDialInternet dialer version 1.53 
--> Initializing modem
--> 
SendingATZ 
ATZ 
OK 
--> SendingATQ0 V1 E1 S0=&C1 &D2 +FCLASS=
ATQ0 V1 E1 S0
=&C1 &D2 +FCLASS=
OK 
--> Modem initialized
--> 
SendingATDT142,1332103001235 
--> Waiting for carrier
ATDT142,1332103001235 
CONNECT 115200 
--> Carrier detected.  Waiting for prompt
User Access Verification 
login

--> 
Looks like a login prompt
--> 
Sendingnolimits 
nolimits 
Password

--> 
Looks like a password prompt
--> 
Sending: (password
Authentication failed
login
--> 
Looks like a login prompt
--> 
Sendingnolimits 
nolimits 
Password

--> 
Looks like a password prompt
--> 
Sending: (password
Authentication failed
login
--> 
Looks like a login prompt
--> 
Sendingnolimits 
--> Dont know what to do!  Starting pppd and hoping for the best
--> 
Starting pppd at Sun Oct 20 13:11:40 2002 
--> pid of pppd1008 
--> Disconnecting at Sun Oct 20 13:11:47 2002 
--> The PPP daemon has diedA 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 
--> Initializing modem
--> 
SendingATZ 
ATZ 
OK 

Above is a copy of what WvDial is echoing to the shell window during execution. Note: I must be logged in a root for it to even get this far. If I was a normal user, I would just get the "resource busy" message.

Eventually I want to use a nice GUI to handle my net connections. So I downloaded gtkDial (which is a Gnome GUI for WvDial), but that program always returns a "resource busy" message, even when I'm logged in as root!!.

I have also made sure my /etc/WvDial.conf is configured correctly, and has correct access privelages set. So at this stage I'm quite frustrated. The only thing that has caught my eye is "CONNECT 115200" which is the baud rate that the modem is using during connect. Would dropping this make a difference.

any help appreciated
advTHANKSance ;)

Mik 10-22-2002 07:21 AM

You mentioned that in Mandrake you had to chmod a few files to get it to work for normal users. Did you do the same on Redhat?

You should check all the permissions of the files which are used by wvdial. It should either be a difference in the users environment or the permissions to access files. Can you check which configuration files are being used when the user calls wvdial. You could always run it with strace to see which files are being opened.

phobos 10-22-2002 11:59 AM

Yes!, AFAIK I've done the exact same chmod(ing) in Red Hat, as I once did in Mandrake, to get this working. Appologies for not making that point clearer before.

WRT strace, I've never used that before, or heard of it for that matter. I just did a "whatis strace" in a shell, to see exactly what it was. But when I get the help up for it, and can't actually understand how it works. I'm not in front of my own box ATM (perhaps later), so I can't test this now. But I'm guessing I will just pass the program name as a parameter to strace, in this case "strace wvdial" (am I right?). It will then give me a list of files that wvdial interacts with during it's execution lifecycle (e.g. /dev/modem, /etc/wvdial.conf).

After I have the list, I just revise the access privaleges (for those files), and try connecting again. If I'm wrong on any of this please correct me. Also if you have any other suggestions, I'm all ears.

Thanks very much for the help, it's greatly appreciated :)


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