Subject: Re: PPP kernel 2.4.x?
From: Iain Stevenson (iain@IainStevenson.com)
Date: Fri Aug 24 2001 - 02:22:45 MDT
OK, so it looks as though wvdial can set up a call but that the login
procedure is not correct. I had problems with the off-the-shelf chat
scripts and ended up using something very simple like:
#!/bin/sh
#
exec /usr/sbin/chat \
ABORT "BUSY" \
ABORT "NO CARRIER" \
ABORT "NO DIALTONE" \
"" AT\&F \
OK ATD0812345678 \
CONN "\c"
Does your ISP use PAP/CHAP? - if so you may need to specify the user ID and
password in a separate file (pap-secrets or chap-secrets). The char-major
messages do not always mean very much since they may refer to an option that
you are not using.
Iain
on 24/8/01 6:47 am, Aake Svensson at aakesve@algonet.se wrote:
Thanks for your attention Iain! Its much appreciated!
... does it actually at any stage cause a dial out on the modem? You
probably need to diagnose the problem in two stages. First, it has to dial,
then it has to start pppd.
No it doesn't dial at all! So I tried wvdial instead with following results:
--> WvDial: Internet dialer version 1.41
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT 95000485570444
--> Waiting for carrier.
ATDT 95000485570444
PROTOCOL: LAP-M
COMPRESSION: V.42BIS
CONNECT 33600
~[7f]}#@!}!1} }8}!}$}&@}%}&I}87.}"}&} } } } }#}$@#OG~
--> Carrier detected. Waiting for prompt.
~[7f]}#@!}!2} }8}!}$}&@}%}&I}87.}"}&} } } } }#}$@#}%U~
--> PPP negotiation detected.
--> Starting pppd at Fri Aug 24 07:24:29 2001
--> PPP daemon has died! (exit code = 2)
--> Disconnecting at Fri Aug 24 07:24:29 2001
--> pppd error! Look at files in /var/log for an explanation.
From /var/log/messages:
<snip>
Aug 24 07:17:01 Linuxserver modprobe: modprobe: Can't locate module
char-major-174
Aug 24 07:17:02 Linuxserver last message repeated 15 times
Aug 24 07:17:02 Linuxserver modprobe: modprobe: Can't locate module
char-major-154
Aug 24 07:17:10 Linuxserver last message repeated 255 times
Aug 24 07:17:10 Linuxserver modprobe: modprobe: Can't locate module
char-major-156
Aug 24 07:17:19 Linuxserver last message repeated 255 times
Aug 24 07:17:34 Linuxserver pppd[1724]: pppd 2.4.1 started by root, uid 0
Aug 24 07:17:35 Linuxserver chat[1725]: abort on (NO CARRIER)
Aug 24 07:17:35 Linuxserver chat[1725]: abort on (NO DIALTONE)
Aug 24 07:17:35 Linuxserver chat[1725]: abort on (ERROR)
Aug 24 07:17:35 Linuxserver chat[1725]: abort on (NO ANSWER)
Aug 24 07:17:35 Linuxserver chat[1725]: abort on (BUSY)
Aug 24 07:17:35 Linuxserver chat[1725]: abort on (WRONG USER/PASSWORD)
Aug 24 07:17:35 Linuxserver chat[1725]: expect ( )
Aug 24 07:18:20 Linuxserver chat[1725]: alarm
Aug 24 07:18:20 Linuxserver chat[1725]: Failed
Aug 24 07:18:20 Linuxserver pppd[1724]: Connect script failed
Aug 24 07:18:21 Linuxserver pppd[1724]: Exit.
Aug 24 07:19:34 Linuxserver modprobe: modprobe: Can't locate module
char-major-174
Aug 24 07:19:34 Linuxserver last message repeated 15 times
Aug 24 07:19:35 Linuxserver modprobe: modprobe: Can't locate module
char-major-154
Aug 24 07:19:43 Linuxserver last message repeated 255 times
Aug 24 07:19:43 Linuxserver modprobe: modprobe: Can't locate module
char-major-156
Aug 24 07:19:51 Linuxserver last message repeated 255 times
Aug 24 07:20:00 Linuxserver CROND[2454]: (root) CMD ( /sbin/rmmod -as)
Aug 24 07:20:21 Linuxserver pppd[2455]: Can't open options file
/etc/ppp/peers/wvdial: No such file or directory
Aug 24 07:23:04 Linuxserver pppd[2458]: Can't open options file
/etc/ppp/peers/wvdial: No such file or directory
Aug 24 07:24:29 Linuxserver pppd[2460]: Can't open options file
/etc/ppp/peers/wvdial: No such file or directory
<end snip>
I see now, for wvdial i'm missing a file - /etc/ppp/peers/wvdial - I'll try
and fix that. But as you can see there's something wrong with either pppd or
chat and modprobe can't find modules char-major-xxx, whatever that means! (I
know theres a module in the pppd package called char-major-108)
Hope that this will shed some light!
Regards,
Aake
Maybe the script to do the dialling is missing some vital piece of
configuration. You could post the scripts you used in this step
> *Reading up on ppp-configuration - "PPP-How to", ISP-Hookup etc etc - found at
> Google etc - and tried writing chatscript in /etc/ppp/ and "isp" script in
> /etc/ppp/peers/
to the list.
Iain
on 23/8/01 1:32 pm, Aake Svensson at aakesve@algonet.se wrote:
>> Aake,
>>
>> on 23/8/01 10:36 am, Aake Svensson at aakesve@algonet.se wrote:
>>
>>> * Trying 'pppd' only. at the command line produces garbled lines of
>>> text until the prompt comes back again.
>>> *Trying exactly to write scripts as recommended in the pppd man page
>>> and running "pppd call 'script' " only gets me back to the prompt
>>> without any delay and/or messages.
>>
>> It's a long time since I used pppd ... but, maybe it's outputting the ppp
>> protocol stuff to the console. It would certainly look like garbled text.
>>
>> I think it's a bit unusual to start pppd from the command line - you'd
>> usually only start it once a modem connection is established using a utility
>> such as 'chat'.
>>
>>
>>
>> Iain
>
>
> I know, I try pppd just to see what's happening and I used to get the
> message about "Kernel lacks ppp support ..., but now it's just
> garbled.
> I've also tried 'ppp call 'script' ' which man pppd recommends and
> that just gives a prompt.
>
> In a new reply to my first mail I've included some error messages
> from dmesg and /var/log/messages, please take a look at them! Hope
> they can shed some light on the matter.
>
> I understand that PPP is not a common Unix/Linux thing as most Linux
> people roam around in large networks or on large servers, but one has
> to start somewhere to learn, especially since the learning curve is
> so fascinating!
>
> Regards,
> Aake Svensson
>
This archive was generated by hypermail 2a24 : Fri Aug 24 2001 - 01:38:55 MDT