Re: ppp fails "LCP: timeout sending Config-Requests"
David Wright wrote:
> Quoting Not Again (p@execulink.com):
> > For the first time I'm having difficulty establishing Linux
> > ppp connections, with a recently opened ISP account.
> > pppconfig has done well enough on my numerous previous
> > setups, with only an occasional script tweak, that I've
> > never had to debug Linux ppp connections before. If I keep
> > trying (without changing my config) I eventually get a good
> > connection, ~1 in 4 times.
> >
> > kernel 2.0.36 pppd version 2.3 patch level 5
> > (I have also tried kernel 2.2.10 pppd 2.3.8; in that case,
> > only ~1 in 10 attempts is successful.)
> >
> >
> > Aug 4 06:57:15 cy4 pppd[180]: Serial connection established.
> > Aug 4 06:57:16 cy4 pppd[180]: Using interface ppp0
> > Aug 4 06:57:16 cy4 pppd[180]: Connect: ppp0 <--> /dev/modem
>
> It may be unrelated, but I would get rid of that link ^^^^^ and
> use the name of the device itself, otherwise you could run into
> device-locking problems.
>
> > Aug 4 06:57:16 cy4 pppd[180]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x8879ba70> <pcomp> <accomp>]
> > Aug 4 06:57:43 cy4 last message repeated 9 times
> > Aug 4 06:57:46 cy4 pppd[180]: LCP: timeout sending Config-Requests
> > Aug 4 06:57:46 cy4 pppd[180]: Connection terminated.
> > Aug 4 06:57:47 cy4 pppd[180]: Exit.
>
> Perhaps PPP is only starting up occasionally at the other end. Do you
> have to issue a ppp command in the chatscript, or should they start
> sending you PPP automatically? Have you checked this by running the
> chatscript by hand yourself using minicom? (PPP looks like garbage
> full of braces {{{.)
>
> Cheers,
>
> --
> Email: d.wright@open.ac.uk Tel: +44 1908 653 739 Fax: +44 1908 655 151
> Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA
> Disclaimer: These addresses are only for reaching me, and do not signify
> official stationery. Views expressed here are either my own or plagiarised.
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
Hello David,
I had the same problem with my ISDN adapter. The problem appeared when I enabled multilink on the device.
The matter is that when turned on multilink, compression was also active. And that was the problem. The remote
access server on my ISP doesn't support any kind of compression. And any attempt to request compression wasn't
replied (although it should), and my adapter keep on sending config-requests.
The solution on my case was disable any kind of compression. May be you'd like to try this. I don't know
how to do that on your modem but on mine was "AT&K00".
Let me know if that works for you.
Reply to: