Next Previous Table of Contents
Did you read the this manual carefully? Here are once more the most common pitfalls.
This means that kppp doesn't have permissions to open the modem device or that you selected a modem device on the Modem Tab Dialog that is not valid. First make sure you selected the right modem device. Once you are sure you have selected the right modem device, you must give kppp the right permission to access the modem device and to be able to modify /etc/resolv.conf in case you want kppp to configure DNS correctly for you. If you can afford to run kppp setuid root this would solve all access problems for you, if not you will have to figure out what the right permissions are for your purposes. In order to give kppp setuid root permissions do the following:
% su root
% chown root:root $(KDEDIR)/bin/kppp
% chmod +s $(KDEDIR)/bin/kppp
% exit
This in most instances means that you have installed kppp without SETUID bit on while you, the person executing kppp, doesn't have write access to the lock file directory which by default is /var/lock. This for example is the case on RedHat systems. Check the modem dialog for the precise location you have chosen. The solution is easy -- either run kppp SETUID if you can afford to, or give regular users write access to /var/lock or create a modem group that will have access to the /var/lock file.
There is no need for the SETUID bit, if you know a bit of Unix systems administration. Simply create a modem group, add all users that you want to give access to the modem to that group and make the modem device read/writeable for that group. Also if you want DNS configuration to work with Kppp, then /etc/resolv.conf must be read/writeable by the members of that group.
Please do not criticize me for installing Kppp with setuid bit on, I simply can no longer handle the amount of mail I used to get from desperate users who had problems getting kppp to work because they didn't understand enough about Unix and device permissions.
Have you played with the CR/LF setting?
Your modem might not sustain a fast initialisation. Increase the 'Init Delay Time' that can be found under 'Modem Commands' on the Modem tab dialog. You may do some fine tuning later.
Just send an empty string such as in the following script:
Send # send an empty string
Expect ID:
Send itsme
Expect word:
Send forgot
Expect granted
Send ppp
This means that you don't have permissions to create a lock file. If for example you have specified '/var/lock/LCK..modem" on the modem dialog tab, you must have write permission to write to /var/lock/. This is of course no problem if you have given kppp setuid permissions. Please read the section on lock files .
Yes you can. Please the see the section on using PAP and CHAP with kppp in the appendix. Actually, I receive more an more requests for detailed information about how to use PAP nor CHAP with kppp. If you are using PAP and CHAP with kppp, I would very much appreciate submissions of detailed step by step explanations of how to do PAP and/or CHAP with kppp. I would then include this here in the kppp documentation. I am sure this would be of help to a great number of beginners. Please consider helping out and giving something back in return for kppp. Thanks!
Just follow the TEMPLATE rules files supplied with kppp. You should be
able to find a copy in the $(KDEDIR)/doc/HTML/kppp
.
Use the -r kppp command line options to check the syntax of your proposed
rules file.
I would love to receive any rule files written. I will make them available on my kppp web page. Before you send me a new rules file make sure it is not already available on the kppp web page. Then email the new rules file to me.
In that case you need to write new code that allows for the computation of that holiday. Please have a look at ruleset.cpp and emulate the ``easter'' example. Then send me the patches.
Next Previous Table of Contents