From: David Jackson <david.jay.jackson@wcox.com>
To: Linux Admin <linux-admin@vger.kernel.org>
Subject: Slack/PPP: LCP: timeout sending Config-Requests
Date: Mon, 29 Apr 2002 09:58:36 -0600 [thread overview]
Message-ID: <3CCD6DAC.AFEB6EEB@wcox.com> (raw)
Howdy --
This one is driving me crazy, I've never had a problem with ppp
connection on Slack-8 before.
What's even more puzzling is It was working on an install which hung
while trying to make bookdisk?
But after *completing* a reinstall, it doesn't? I've tried PAP and CHAP
(pap works on Debian and Redhat). Note it connect, but doesn't add
routing for IP assigned by ISP?
TIA,
David
I'm using a USRobotics external modem.
Here's the error messages:
slacker:root >> ppp-go
/etc/ppp
slacker:root >> Serial connection established.
Using interface ppp0
Connect: ppp0 <--> /dev/ttyS1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x71cdcf1e> <pcomp>
<accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x71cdcf1e> <pcomp>
<accomp>]
LCP: timeout sending Config-Requests
Here's my options.
lock
defaultroute
noipdefault
modem
/dev/ttyS1
57600
crtscts
# Uncomment the line below for more verbose error reporting:
debug
# If you have a default route already, pppd may require the other side
# to authenticate itself, which most ISPs will not do. To work around
this,
# uncomment the line below. Note that this may have negative side
effects
# on system security if you allow PPP dialins. See the docs in
/usr/doc/ppp*
# for more information.
#noauth
passive
asyncmap 0
name "david.jay.jackson"
next reply other threads:[~2002-04-29 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 15:58 David Jackson [this message]
2002-04-30 5:55 ` Slack/PPP: LCP: timeout sending Config-Requests Camelia NASTASE
-- strict thread matches above, loose matches on Subject: below --
2002-04-30 6:25 David Jackson
2002-04-30 9:18 ` Camelia NASTASE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CCD6DAC.AFEB6EEB@wcox.com \
--to=david.jay.jackson@wcox.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).