I've seen that intermittently with all kernel builds I've used, so
it's not specific to 2.3.99pre6. It also appears to me, or perhaps
I'm imagining things, that later kernel builds get less and less
tolerant of sloppy PPP configurations. I've generally been able to
eliminate the errors by tweaking things.
I have not used that kernel build of yours (tried, failed, finicky
laptop), so if none of what follows is relevant, please forgive me.
It may be, however, that more careful configuration could avoid
problems, as it sometimes has for me. Since I've settled on the
configuration below, I never see that cursed LCP error.
Are you using a pap-secrets file? At one time, I had everything in a
demand-dial script, and one of my two providers caused that error
you're seeing until I switched to a separate
pap-secrets/options/chatfile setup. My scripts are below. These
work well for all my service providers under 2.2.14, pppd 2.3.7.
/etc/ppp/chatfile:
ABORT 'NO CARRIER'
ABORT 'NO DIALTONE'
ABORT 'ERROR'
ABORT 'NO ANSWER'
ABORT 'BUSY'
""
ATDT5551212 CONNECT
OK
/etc/ppp/options:
/dev/modem
38400 #Make this a valid port speed!
crtscts
lock
connect "/usr/sbin/chat -vf /etc/ppp/chatfile"
defaultroute
name username
noipdefault
/etc/ppp/demand:
exec /usr/sbin/pppd demand idle 3600 ipcp-accept-remote ipcp-accept-local \
192.168.1.1:10.0.0.1 defaultroute
/etc/ppp/pap-secrets:
username * password
-David
-------------------------------------------------------------
Steven W. Orr wrote:
:I'm running ppp-2.3.10-3. When I tried to go from 2.2.14 of linux to
:2.3.99pre6, everything seemed to be ok until I tried to connect to my
:ISP. Then I get the following snippet:
:
:Apr 28 20:16:02 localhost connect: Initializing Modem
:Apr 28 20:16:02 localhost connect: Dialing 4299300
:Apr 28 20:16:27 localhost connect: chat: Apr 28 20:16:26 CONNECT
:115200
:Apr 28 20:16:27 localhost connect: Protocol started
:Apr 28 20:16:27 localhost diald[352]: Running pppd (pid = 738).
:Apr 28 20:16:27 localhost kernel: PPP generic driver version 2.4.1
:Apr 28 20:16:27 localhost pppd[738]: pppd 2.3.10 started by root, uid
:0
:Apr 28 20:16:27 localhost pppd[738]: Using interface ppp0
:Apr 28 20:16:27 localhost pppd[738]: Connect: ppp0 <--> /dev/ttyS0
:Apr 28 20:16:57 localhost pppd[738]: LCP: timeout sending Config-Requests
:Apr 28 20:16:57 localhost pppd[738]: Connection terminated.
:Apr 28 20:16:57 localhost pppd[738]: Exit.
:
:This problem has to be fixed. I checked dejanews and there are people
:getting this problem, but no answer on how to fix it. Here's my
:/etc/ppp/options file:
:
:1010 > cat options
:lock noauth
:user steveo
:
:I'd also like to add one more comment to the mix: I have two
:modems. One is a Motorola VoiceSURFER. The other is on my wife's
:identical computer. Her's is a USR V.90. Both are external. I tried
:to move her modem onto my computer a while back and had the same
:error. It went away when I restored my Motorola.
:
:I really don't even know how to start debugging this.
:
:Anyone have a clue?
:
:Many thanks in advance.
:
:
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
