LCP: timeout sending Config-Requests

LCP: timeout sending Config-Requests

Post by digitalklow » Mon, 26 Apr 1999 04:00:00



hi i keep getting this:

Apr 19 22:22:03 localhost kernel: PPP Dynamic channel allocation code
copyright 1995 Caldera, Inc.
Apr 19 22:22:03 localhost kernel: PPP line discipline registered.
Apr 19 22:22:03 localhost kernel: registered device ppp0
Apr 19 22:22:03 localhost pppd[473]: pppd 2.3.5 started by root, uid 0
Apr 19 22:22:04 localhost chat[478]: abort on (BUSY)
Apr 19 22:22:04 localhost chat[478]: abort on (ERROR)
Apr 19 22:22:04 localhost chat[478]: abort on (NO CARRIER)
Apr 19 22:22:04 localhost chat[478]: abort on (NO DIALTONE)
Apr 19 22:22:04 localhost chat[478]: abort on (Invalid Login)
Apr 19 22:22:04 localhost chat[478]: abort on (Login incorrect)
Apr 19 22:22:04 localhost chat[478]: send (AT&F^M)
Apr 19 22:22:04 localhost chat[478]: expect (OK)
Apr 19 22:22:23 localhost chat[478]: AT&F^M^M
Apr 19 22:22:23 localhost chat[478]: OK
Apr 19 22:22:23 localhost chat[478]:  -- got it
Apr 19 22:22:23 localhost chat[478]: send (ATDT*70,3533539^M)
Apr 19 22:22:23 localhost chat[478]: expect (CONNECT)
Apr 19 22:22:23 localhost chat[478]: ^M
Apr 19 22:23:03 localhost chat[478]: ATDT*70,3533539^M
Apr 19 22:23:03 localhost pppd[473]: Serial connection established.
Apr 19 22:23:03 localhost chat[478]: CONNECT
Apr 19 22:23:03 localhost chat[478]:  -- got it
Apr 19 22:23:03 localhost chat[478]: send (^M)
Apr 19 22:23:13 localhost pppd[473]: Using interface ppp0
Apr 19 22:23:13 localhost pppd[473]: Connect: ppp0 <--> /dev/modem
Apr 19 22:23:13 localhost pppd[473]: sent [LCP ConfReq id=0x1 <magic
0xb364558d> <pcomp> <accomp>]
Apr 19 22:23:40 localhost last message repeated 9 times
Apr 19 22:23:43 localhost pppd[473]: LCP: timeout sending Config-Requests
Apr 19 22:24:31 localhost xntpd[315]: synchronized to LOCAL(0), stratum=0
Apr 19 22:24:53 localhost pppd[473]: Modem hangup
Apr 19 22:24:53 localhost pppd[473]: Connection terminated.

i tried
CONNECT '/d/c'

thanks
/jgh

 
 
 

LCP: timeout sending Config-Requests

Post by Clifford Ki » Mon, 26 Apr 1999 04:00:00


: Apr 19 22:22:04 localhost chat[478]: send (AT&F^M)
: Apr 19 22:22:04 localhost chat[478]: expect (OK)
: Apr 19 22:22:23 localhost chat[478]: AT&F^M^M
: Apr 19 22:22:23 localhost chat[478]: OK
: Apr 19 22:22:23 localhost chat[478]:  -- got it

Look at the time stamps.  There is a 19 second delay between the time
the modem commands are sent and the time the OK from the modem is
received.  It should be no more than one second.

This means that the IRQ configured in Linux for the modem's device file is
not the IRQ that the modem actually uses.  Configuration is usually done
at boot-up by setserial in a in /ect/rc.* .  Doing "setserial /dev/ttySx"
will tell you the configured IRQ, where ttySx is the modem device file.
Determining the IRQ the modem actually uses is up to you.

..

: i tried
: CONNECT '/d/c'

Stick with this form.

--

/* Governments should be changed like diapers - often and for the
 * same reason. */

 
 
 

LCP: timeout sending Config-Requests

Post by Clifford Ki » Mon, 26 Apr 1999 04:00:00


:     Apr 24 06:00:55 perry chat[1260]: send (AT^M)
:     Apr 24 06:00:55 perry chat[1260]: expect (OK)
:     Apr 24 06:01:14 perry chat[1260]: AT^M^M
:     Apr 24 06:01:14 perry chat[1260]: OK
:     Apr 24 06:01:14 perry chat[1260]:  -- got it

This is the worse problem.  Look at the timestamps, there is a 19 second
delay between the time AT is sent and the modem response OK is received.
It should be less than one second.

This means that the IRQ configured in Linux for the modem's device file is
not the IRQ that the modem actually uses.  Configuration is usually done
at boot-up by setserial in a in /ect/rc.* .  Doing "setserial /dev/ttySx"
will tell you the configured IRQ, where ttySx is the modem device file.
Determining the IRQ the modem actually uses is up to you.

: I momentarily digress from the log, to point out a side issue (though
: it may be the real problem in my case).  Note the significant delay
: (~19 sec) from the time the log shows "sent (AT^M)" and the time the
: modem apparently notices it.  All the commands are this way,

You did notice it, I didn't read far enough.

--

 
 
 

LCP: timeout sending Config-Requests

Post by Joost Everts » Tue, 27 Apr 1999 04:00:00




> : Apr 19 22:22:04 localhost chat[478]: send (AT&F^M)
> : Apr 19 22:22:04 localhost chat[478]: expect (OK)
> : Apr 19 22:22:23 localhost chat[478]: AT&F^M^M
> : Apr 19 22:22:23 localhost chat[478]: OK
> : Apr 19 22:22:23 localhost chat[478]:  -- got it

> Look at the time stamps.  There is a 19 second delay between the time
> the modem commands are sent and the time the OK from the modem is
> received.  It should be no more than one second.

> This means that the IRQ configured in Linux for the modem's device file is
> not the IRQ that the modem actually uses.  Configuration is usually done
> at boot-up by setserial in a in /ect/rc.* .  Doing "setserial /dev/ttySx"
> will tell you the configured IRQ, where ttySx is the modem device file.
> Determining the IRQ the modem actually uses is up to you.

> ..

> : i tried
> : CONNECT '/d/c'

> Stick with this form.

Hello,

I had exactly this problem, and the solution was indeed changing the irq on
te modem (or /dev/modem). I already wondered why in Minicom the modem reacted
so incredibly slow. But at first i thought that was because of a
configuration setting. I thougt that chat wouldn't have that problem. Then i
saw your postings, and checked /var/log/messages for time outs, and then i
did a  setserial /dev/modem, and tada , it said 3e8 irq4. And  modem actually
is at 3e8 5. I changed the irq.
Now it all works fine.
I want to thank you for your postings, and i will try to contribute  myself.

Regards from Holland,
Joost Evertse

- Show quoted text -

> --

> /* Governments should be changed like diapers - often and for the
>  * same reason. */

 
 
 

1. LCP: timeout sending Config-Requests - more info

I am receiveing this error messagecould anyone give me any pointers or a
place
where I can find information on how to solve this problem.
I have checked in pppdocs and can find nothing mentioned about this.

LCP: timeout sending Config-Requests

Connect appears to be made correctly up to the point where
it would go into ppp mode on my side. I am tryn to kppp to connect.

Below are the logs and script files, I am using.

------------------------------------
(Is in the login script debug window, terminal mode)
CONNECT 38400
login: XXXXXX
Password: XXXXXX
 Entering PPP Mode.
 IP address is XXX.XXX.XXX.XXX
 MTU is 1524.

(Is in the PPP-logfile  -minus the system info)
pppd 2.3.7 started by root, uid 0
Using interface ppp0
Connect: ppp0 <--> /dev/ttyS0
LCP: timeout sending Config-Requests
Connection terminated.
Connect time 0.9 minutes.
Exit.

(Is in chat-ppp0)
'ABORT' 'BUSY'
'ABORT' 'ERROR'
'ABORT' 'NO CARRIER'
'ABORT' 'NO DIALTONE'
'ABORT' 'Invalid Login'
'ABORT' 'Login incorrect'
'' 'ATZ'
'OK' 'ATDTXXXXXXX'
'CONNECT' ''
'ogin:' 'XXXXXX'
'ord:' 'XXXXXX'
'TIMEOUT' '5'
'~--' ''

2. Powerbook G3 bronze 400Mhz

3. pppd fails with: LCP: timeout sending Config-Requests

4. Need to know companies that are using Linux for developement of apps.

5. Rehat 4.0 ppp: "LCP: timeout sending Config-Requests"

6. How do I compile my ethernet driver?

7. LCP: timeout sending Config-Requests

8. : S3 and intermediate resolution between 1280x1024 and 1600x1200 ?

9. PPP - LCP timeout sending Config-Requests

10. PPP Prob - LCP: timeout sending Config-requests

11. pppd -> LCP: timeout sending Config-Requests ???

12. LCP: timeout sending Config-Requests

13. LCP: timeout sending Config-Requests (PPP problem?)