Re: How to start PPP?
At 11:34 PM 9/16/1998 -0300, you wrote:
>On Wed, Sep 16, 1998 at 08:11:51PM -0500, Kent West wrote:
>> Okay; I give up on the documentation. Maybe someone on the list can help.
>>
>> I've got a minimal Debian 2.0 system up and running (base install from the
>> floppies and that's it). I've run pppconfig and told it to create a
>> connection named "bub". I haven't found any documentation that tells me how
>> to use this connection. I've found several references to running pon, or
>> pppd, and references to chatscript and provider and etc etc etc.
>>
>> I've figured out that if I just type pon the system tries to use the
>> "provider" connection (which doesn't work, presumably because the
>> "provider" files aren't properly configured - it gives an error message
>> about /dev/modem being an unrecognized option). But if I type pon bub
>> (which is what I would have thought would've used the "bub" connection),
>> all that happens is the system thinks for a couple of seconds and then
>> returns me to a prompt. There's no modem activity or messages or anything.
>
>If you are not running "pon bub" as root, then the problem appears to
>be related to wrong permissions on the system files and the requirement
>for users using pppd to be in the proper group (/etc/group):
>
> The ppp files permissions under Debian 2.0 should look like this:
>
> drwx--x--- 2 root dip /etc/chatscripts/
> -rw-r----- 1 root dip /etc/chatscripts/provider
> drwx--x--- 5 root dip /etc/ppp/
> -rw------- 1 root root /etc/ppp/options
> -rw------- 1 root root /etc/ppp/pap-secrets
> -rw------- 1 root root /etc/ppp/chap-secrets
> drwx--x--- 2 root dip /etc/ppp/peers/
> -rw-r----- 1 root dip /etc/ppp/peers/provider
> -rws--x--- 1 root dip /usr/sbin/pppd
> -rwxr-x--- 1 root dip /usr/bin/pon
> -rwxr-x--- 1 root dip /usr/bin/poff
> crw------- 1 root root /dev/ttyS2
>
> Put the users who are to bring up a ppp link in the dip group.
>
> As shipped Debian 2.0 has /etc/chatscripts like this:
>
> drwx------ 2 root dip /etc/chatscripts/
>
> This is a known bug -- wrong permissions on /etc/chatscripts/.
>
> (quoted from a message on debian-user)
>
>
>--
> jkern@klis.com Jack Kern Yarmouth, Nova Scotia Debian GNU/Linux
I am running it as root.
Since this is a new installation, I decided to wipe the drive and do
another install. I also decided to stick with the defaults and use the name
"provider" instead of "bub". Now pon is doing the same thing; the system
thinks for a minute and then returns me to the prompt.
When I do a "ps a", it shows that "/usr/bin/ppd call provider" and
"usr/sbin/chat -v -f /etc/chatscripts/provider" are running on tty S1 with
a stat of S and a time of 0:00. If I wait a couple of minutes and do
another "ps a", they are no longer there.
The permissions on the files (just after the new install) are as follows:
drwxr-s--- 2 root dip /etc/chatscripts/
-rw-r----- 1 root dip /etc/chatscripts/provider
drwx------ 5 root root /etc/ppp/
-rw-r--r-- 1 root root /etc/ppp/options
-rw------- 1 root root /etc/ppp/pap-secrets
-rw------- 1 root root /etc/ppp/chap-secrets
drwxr-s--- 2 root dip /etc/ppp/peers
-rw-r----- 1 root dip /etc/ppp/peers/provider
-rwsr-xr-- 1 root dip /usr/bin/pppd
-rwxr-xr-x 1 root root /usr/bin/pon
-rwxr-xr-x 1 root root /usr/bin/poff
crw-rw---- 1 root dialout /dev/ttyS1
I notice the permissions aren't quite the same as what you listed, so I'll
try playing with those in a few minutes.
I can "echo ATDT<phonenum> > /dev/ttyS1" and I can hear the modem dial and
the phone in the other room ring. Then I can "echo ATZ > /dev/ttyS1" and it
hangs up, so I know the hardware is working.
I'll send another message to the list in response to John Hasler with a
listing of some of the pertinent files.
Thanks!
===========================================================
Kent West | Technology Support/ |
Abilene Christian University | Voice: 915-674-2557 FAX: 915.674.6724 |
ACU Station, Box 29005 | E-MAIL: kent.west@infotech.acu.edu |
Abilene, TX 79699-9005 | Ham: KC5ENO, General |
===========================================================
Reply to: