[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ppp failure under debian (slakware with pppd 2.2 patch level 0 works)



On Sat, Sep 18, 1999 at 05:06:18PM +1000, Robert.King@mailbox.gu.edu.au wrote:
> Hi,
>    I'm typing this from my old slackware install.  I connect on this
> installation using cu -l /dev/cua1 then negotiating my way through my
> ISP's login manually, then start pppd in another window, then quitting
> from cu.  This worked fine whne this machine was a 486 and now works with
> a new motherboard & cpu.  
> 
> I tried installing potato on the machine, and most things are going fine,
> except that sound isn't working on the new setup, and ppp won't work on
> it.  
> 
> I'm fairly sure that the serial conifg is OK, as I can get out with 
> cu -l /dev/ttyS1, but when I try to start pppd, it complains about cu
> having the serial line and won't let it at it.
> 
> As far as using pon, I get the following :
> 
> 
> Aug  4 19:16:00 castle kernel: PPP: version 2.2.0 (dynamic channel allocation) 
> Aug  4 19:16:00 castle kernel: PPP Dynamic channel allocation code copyright 199
> 5 Caldera, Inc. 
> Aug  4 19:16:00 castle kernel: PPP line discipline registered. 
> Aug  4 19:16:00 castle kernel: registered device ppp0 
> Aug  4 19:16:00 castle pppd[620]: pppd 2.3.8 started by robert, uid 1000
> Aug  4 19:16:01 castle chat[621]: abort on (BUSY)
> Aug  4 19:16:01 castle chat[621]: abort on (NO CARRIER)
> Aug  4 19:16:01 castle chat[621]: abort on (VOICE)
> Aug  4 19:16:01 castle chat[621]: abort on (NO DIALTONE)
> Aug  4 19:16:01 castle chat[621]: abort on (NO DIAL TONE)
> Aug  4 19:16:01 castle chat[621]: abort on (NO ANSWER)
> Aug  4 19:16:01 castle chat[621]: send (ATZ^M)
> Aug  4 19:16:01 castle chat[621]: expect (OK)
> Aug  4 19:16:46 castle chat[621]: alarm
> Aug  4 19:16:46 castle chat[621]: send (AT^M)
> Aug  4 19:16:46 castle chat[621]: expect (OK)
> Aug  4 19:17:31 castle chat[621]: alarm
> Aug  4 19:17:31 castle chat[621]: Failed
> Aug  4 19:17:32 castle pppd[620]: Exit.
> Aug  4 19:18:00 castle kernel: PPP: ppp line discipline successfully unregistere

first thing: should there be any chat script at all if you authenticate
using cu? (i've never used cu, so i may be wrong)
Should the chat script try to reset the modem if it has already connected??
(the ATZ and AT)

I would try to edit /etc/chatscripts/provider to contain only one line:
'' ''
if I were you.

> One thing that concerned me was that the kernel messages from dmesg don't
> mention the ppp0 device as happens on a working debian ppp machine I've seen.
> The relevant part of dmesg looks like this ....
> 
> PPP: version 2.3.7 (demand dialling)
> PPP line discipline registered.
> 
> and that's it.
> 
> What is happening?

this is how it looks like on my system (slink, 2.2.12):

PPP: version 2.3.7 (demand dialling)
PPP line discipline registered.
registered device ppp0
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP: ppp line discipline successfully unregistered

and as far as i can remember, the "registered device ppp0" appears only
after chat script has finished successfully:

Sep 18 12:56:04 pecet pppd[166]: Serial connection established.
Sep 18 12:56:05 pecet pppd[166]: Using interface ppp0

hope this helps,
Marcin

-- 

--------------------------------
Marcin Owsiany
porridge@pandora.info.bielsko.pl
--------------------------------


Reply to: