This is a discussion on Re: pppd daemon dying within the Linux Networking forums, part of the Linux Forums category; On Sat, 12 Jun 2004 06:26:49 +0000, Cryptic Lineage wrote: > pppd dies the moment it is launched. ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On Sat, 12 Jun 2004 06:26:49 +0000, Cryptic Lineage wrote:
> pppd dies the moment it is launched. Please see following description. > I am hoping to have some feedback. This is specific to gnome. If I > use kppp under kde, I can connect just fine, there is no problem whatsoever. How about kppp under GNOME? Does that work? I never used either, but IIUC wvdial and kppp are each simply frontends for the same pppd. Slackware has a simplified frontend called "pppsetup". Did you try that one? "ppp-go" (as root of course) is the command to connect. > I checked what exit code 2 means. From man pppd: > > 2 An error was detected in processing the options > given, such as two mutually exclusive options being > used. > > Now I dont know what that means. Here are my options from /etc/ppp/options: > > root@enigma:/home/vikram# egrep -v '#|^ *$' /etc/ppp/options > asyncmap 0 > crtscts > lock > modem > proxyarp > lcp-echo-interval 30 > lcp-echo-failure 4 Nice touch, to bypass the comments. :) Thank you. Add "debug" to those options and /var/log/debug will contain a detailed account of the dialogue between your pppd and the Sprint dialup server. You can also look up each of those options in "man pppd" and find out about them. The one I think suspicious, that I don't remember from my dialup days, is proxyarp. That's used so the remote will appear to be on your local Ethernet segment. I don't think you want that. Floyd Davidson, who posts here, and Clifford Kite, who posts in comp.os.linux.networking, are very good at troubleshooting PPP problems. For the benefit of Mr. Kite ;) I've crossposted this. -- /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net or put "not-spam" or "/dev/rob0" in Subject header to reply |
|
|||
|
/dev/rob0 <rob0@gmx.co.uk> wrote:
> On Sat, 12 Jun 2004 06:26:49 +0000, Cryptic Lineage wrote: >> pppd dies the moment it is launched. Please see following description. >> I am hoping to have some feedback. This is specific to gnome. If I >> use kppp under kde, I can connect just fine, there is no problem whatsoever. You are using the wvdial front-end to pppd. One thing to try is to configure it with "Stupid Mode = 1" (yes, there is such a wvdial configuration item - rather badly named..) in order to use PAP or CHAP authentication within PPP negotiations. Just because you can do login/password doesn't mean that is what you should do; it may be reserved for people other than regular clients. I don't use wvdial or any other front-end to pppd, except my own shell script. So make sure the options include "user YourISPusername" and the line YourISPusername * YourISPpassword is in both files /etc/ppp/{chap,pap}-secrets when Stupid Mode is turned on. > How about kppp under GNOME? Does that work? I never used either, but > IIUC wvdial and kppp are each simply frontends for the same pppd. > Slackware has a simplified frontend called "pppsetup". Did you try that > one? "ppp-go" (as root of course) is the command to connect. >> I checked what exit code 2 means. From man pppd: >> >> 2 An error was detected in processing the options >> given, such as two mutually exclusive options being >> used. >> >> Now I dont know what that means. Here are my options from /etc/ppp/options: It means that there's a bad option, or that there are conflicting options (the "mutually exclusive" - which, IMHO, is not a good way to describe it). >> root@enigma:/home/vikram# egrep -v '#|^ *$' /etc/ppp/options >> asyncmap 0 >> crtscts >> lock >> modem >> proxyarp >> lcp-echo-interval 30 >> lcp-echo-failure 4 Nothing wrong here, except that you don't need proxyarp. Well, better make that nothing wrong unless you are attempting to use a cell-phone, and there I can't help. PPP implementations by cell-phone companies do weird things. Such as: you may need both the login/password dance and PAP or CHAP authentication as well. > Nice touch, to bypass the comments. :) Thank you. > Add "debug" to those options and /var/log/debug will contain a detailed > account of the dialogue between your pppd and the Sprint dialup server. And also add the "dump" option to see if there are options configured that are not in /etc/ppp/options. The options should be in a log file, perhaps /var/log/messages - unless Slackware has changed it's configuration for the /etc/syslog.conf file recently. > You can also look up each of those options in "man pppd" and find out > about them. The one I think suspicious, that I don't remember from my > dialup days, is proxyarp. That's used so the remote will appear to be > on your local Ethernet segment. I don't think you want that. You only want that if you are accepting calls for a dial-in and want it to communicate with hosts on a LAN, not when connecting to an ISP for Internet access. -- Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13" PPP-Q&A links, downloads: http://ckite.no-ip.net/ /* The signal-to-noise ratio is too low in many [news] groups to make * them good candidates for archiving. * --- Mike Moraes, Answers to FAQs about Usenet */ |