Subject: Re: LCP timeout sending Config-Requests
To: None <tech-net@netbsd.org>
From: Martin Gerbing <martin@gerbing.net>
List: tech-net
Date: 12/18/2001 15:09:23
Hello again,
thanks for the hints. I tried it but it is still the same.
For a better description of my problem I write my /etc/ppp/options down:
# /etc/ppp/options
lock
crtscts
115200
modem
defaultroute
noipdefault
And here is my /etc/ppp/peers/provider:
# /etc/ppp/peers/provider
connect '/usr/sbin/chat -v -f /etc/ppp/peers/provider.chat'
noauth
user myusername
remotename provider
And here is my /etc/ppp/peers/provider.chat:
# /etc/ppp/peers/provider.chat
ABORT BUSY
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
'' ATZ OK
'' ATDT010900191799 # Phonenumber of provider
TIMEOUT 500
connect ''
ogin: myloginname
ssword: mypassword
On my prompt I enter:
:> pppd call provider
Then the following message comes:
Serial connection established
Using interface ppp0
Connect: ppp0 <--> /dev/tty01
and after a time (~ 5 minutes) the following is written to me:
LCP: timeout sending Config-Requests
By an other provider there comes only trash back to me (noreadable lines :(( ).
I don't know more :(
Does anybody can help me, please?
Thanks for all your help and hints.
Martin
On Sun, Dec 16, 2001 at 06:00:46PM -0600, Frederick Bruckman wrote:
> On Mon, 17 Dec 2001, Manuel Bouyer wrote:
>
> > On Sun, Dec 16, 2001 at 09:33:16PM +0100, Martin Gerbing wrote:
> > > Hello,
> > >
> > > I installed NetBSD 1.5.2 and after installing the pppd I tried to connect to
> > > my ISP. But every time after my chat script were running the following
> > > message appears and I am disconnected:
> > >
> > > LCP timeout sending Config-Requests
> > >
> > > I tried the init script:
> > >
> > > pppd tty01 115200 modem crtscts init "chat '' ATZ OK ATS0=1 OK"
> >
> > Hum, this doesn't make chat dial out, or did I miss something ?
>
> Perhaps that should be "ATDTS=0"? Such would dial the number saved
> with "at&z0=nnnnnnn&w0".
>
> Even so, the script will start sending LCP requests while the modem is
> dialing. Better to change that last OK to wait for "ONNECT" or "ogin:",
> to let the terminal server answer first.
>
> Frederick