Steve Scrimpshire Posted May 31, 2003 Report Share Posted May 31, 2003 I talk a little about this in my venting topic in the Linux forum, but for help, I thought I should post here. Attempting to run wvdial, I get a pppd error (var/log/messages): May 31 17:15:46 localhost pppd[5642]: pppd 2.4.1 started by root, uid 0 May 31 17:15:46 localhost pppd[5642]: Using interface ppp0 May 31 17:15:46 localhost pppd[5642]: Connect: ppp0 <--> /dev/ttyS0 May 31 17:15:46 localhost /etc/hotplug/net.agent: assuming ppp0 is already up May 31 17:16:01 localhost CROND[5652]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner) May 31 17:16:06 localhost pppd[5642]: Hangup (SIGHUP) May 31 17:16:06 localhost pppd[5642]: Modem hangup /etc/ppp/options: lock debug noauth noipdefault usepeerdns defaultroute /etc/ppp/peers/wvdial: noauth name wvdial usepeerdns I've tried changing /etc/ppp/peers/wvdial to read just like /etc/ppp/options, but the same thing happens. /etc/wvdial.conf: [Dialer Defaults] Modem = /dev/modem Baud = 115200 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Stupid mode = yes Modem Type = Analog Modem Phone = <<do you think I'm gonna post the real stuff here?>> Username = <<do you think I'm gonna post the real stuff here?>> Password = <<do you think I'm gonna post the real stuff here?>> ISDN = 0 Modem Type = Analog Modem Note: kppp works fine. /var/log/messages: May 31 15:52:19 localhost pppd[13400]: pppd 2.4.1 started by omar, uid 502 May 31 15:52:19 localhost pppd[13400]: Using interface ppp0 May 31 15:52:19 localhost pppd[13400]: Connect: ppp0 <--> /dev/ttyS0 May 31 15:52:23 localhost pppd[13400]: local IP address <<ip here>> May 31 15:52:23 localhost pppd[13400]: remote IP address <<ip here>> May 31 15:52:23 localhost pppd[13400]: primary DNS address <<DNS address here>> May 31 15:52:23 localhost pppd[13400]: secondary DNS address <<DNS address here>> Here's the output of the terminal I'm running wvdial from: # wvdial --> 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<<phone number>> --> Waiting for carrier. ATDT<<phone number>> CONNECT 115200 C UQKT2 User Access Verification Username: --> Carrier detected. Starting PPP immediately. --> Starting pppd at Sat May 31 17:18:21 2003 --> pid of pppd: 5672 --> Disconnecting at Sat May 31 17:18:57 2003 --> 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 Quote Link to comment Share on other sites More sharing options...
bvc Posted May 31, 2003 Report Share Posted May 31, 2003 I don't think it matters but...you have; Modem Type = Analog Modem in there twice. Have you #commented out ISDN = 0 Modem Type = Analog Modem and tried it. I was able to keep; Modem Type = Analog Modem but had to remove ISDN = 0 Quote Link to comment Share on other sites More sharing options...
ramfree17 Posted May 31, 2003 Report Share Posted May 31, 2003 mine worked when i removed the analog modem option, and added the Auto DNS and Stupid Mode options. i can now connect to the internet faster since i dont have to wait for kpp to startup its kde services. :#: but then again, im on a sucky dialup and not ISDN. :( ciao! Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 1, 2003 Author Report Share Posted June 1, 2003 Yup, tried removing it. Quote Link to comment Share on other sites More sharing options...
bvc Posted June 1, 2003 Report Share Posted June 1, 2003 Did you ever try linuxconf/wvdial to see if would fix it ? Since it's not working anyway how about; Find out the group ownership of (I believe daemon) /etc/wvdial.conf /etc/ppp/peers/wvdial and add your user to the group daemon. Not a good idea? Create a group...oh say dialout, or dial and change the group ownership to the above to the new group, then add your user to the new group. Then copy the following into a terminal and hit enter chmod +s /usr/bin/wvdial && chmod +x /usr/sbin/pppd && chmod +s /usr/sbin/pppd This is how wvdial is set up in my Libranet-2.8. It already had the group ownership of dialout, I just added bvc to it in /etc/group; dialout:*:20:bvc Then all I had to do was the above chmods. I did this same thing in 9.0 except the group I created was 'wvdial'.....it worked :wink: Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 1, 2003 Author Report Share Posted June 1, 2003 What do you mean "Did you ever try linuxconf/wvdial to see if would fix it" ? Quote Link to comment Share on other sites More sharing options...
bvc Posted June 1, 2003 Report Share Posted June 1, 2003 http://www.mandrakeusers.org/viewtopic.php?t=5483 In linuxconf>Networking (or Network) you can tell it to use wvdial. It kinda messes with the format and adds its own entries to the wvdial.conf file, but you can change it back. Maybe trying it will kick something into place? Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 1, 2003 Author Report Share Posted June 1, 2003 Ok, I tried all that. Once again, kppp works fine, so I know it's not a problem with my /etc/ppp/options or anything. I believe that wvdial does not recognize that there is a prompt for the username. Notice how it says "Waiting for prompt" after 'Username' prompt is given. I think the remote server is prompting too quick for wvdial or something. Every once in a while, wvdial will connect properly. one in a hundred times, I'd say. Sometimes I see it see it send '+++' when prompted for a username. I've tried adding Login Prompt = Username: Login Prompt = sername: tried changing Username to Login in wvdial.conf tried adding Default Reply = my username nothing. Various errors. Sometimes it's error 10, sometimes 16, sometimes 2 Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 1, 2003 Author Report Share Posted June 1, 2003 http://www.mandrakeusers.org/viewtopic.php?t=5483 In linuxconf>Networking (or Network) you can tell it to use wvdial. It kinda messes with the format and adds its own entries to the wvdial.conf file, but you can change it back. Maybe trying it will kick something into place? I don't see the option to tell it to use wvdial in Linuxconf -> Networking. What exactly do you mean? Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 3, 2003 Author Report Share Posted June 3, 2003 wvdial just suddenly started working again. I figure it's one, some or all of three things: [*] My ISP changed something [*] Adding devfs=nomount to my lilo.conf append line fixed it (I did it for a totally different reason and haven't tried wvdial for awhile) [*] I got lucky Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.