On Sat, 18 Dec 1999, Tamer S. Embaby wrote:
|Sorry, this message has to be long. I cannot connect to my ISP, which
|claim to use CHAP authentication, I'm using SuSE 6.1 kernel 2.2.7, pppd
|v2.3.5.
It might be a good idea to upgrade the kernel since I think there
was something slightly wrong with the kernel PPP support prior to
the 2.2.8 kernel. But I don't think that's your current problem.
|# /var/log/messages
[snip]
|Dec 18 16:06:02 tita pppd[529]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
|<magic 0x728487f2> <pcomp> <accomp>]
|Dec 18 16:06:11 tita last message repeated 3 times
|Dec 18 16:06:11 tita kernel: ppp: receive buffer, count = 15
|Dec 18 16:06:11 tita kernel: FF 7D 23 C0 21 7D 21 7D .}#.!}!}
|Dec 18 16:06:11 tita kernel: 21 7D 20 7D 3F 7D 21 !} }?}!
This is the beginning of a frame with an LCP request from the peer
that contained errors.
|Dec 18 16:06:14 tita pppd[529]: LCP: timeout sending Config-Requests
|Dec 18 16:06:14 tita pppd[529]: Connection terminated.
|Dec 18 16:06:21 tita kernel: ppp: receive buffer, count = 15
|Dec 18 16:06:21 tita kernel: FF 7D 23 C0 21 7D 21 7D .}#.!}!}
|Dec 18 16:06:21 tita kernel: 21 7D 20 7D 3F 7D 21 !} }?}!
|Dec 18 16:06:31 tita kernel: ppp: receive buffer, count = 15
|Dec 18 16:06:31 tita kernel: FF 7D 23 C0 21 7D 22 7D .}#.!}"}
|Dec 18 16:06:31 tita kernel: 21 7D 20 7D 34 7D 22 !} }4}"
This is the beginning of an ACK of the LCP request that pppd sent
repeatedly. It came after pppd has already sent all the repeat LCP
requests that it's configured to send.
|Dec 18 16:06:40 tita kernel: ppp: channel ppp0 closing.
|Dec 18 16:06:40 tita kernel: ppp0 released
|Dec 18 16:06:40 tita kernel: ppp0: ccp closed
|Dec 18 16:06:40 tita pppd[529]: Hangup (SIGHUP)
|Dec 18 16:06:40 tita pppd[529]: ioctl(TIOCSETD, N_TTY): Interrupted
|system call
|Dec 18 16:06:41 tita pppd[529]: Exit.
|
|Sometimes i get:
|>>> [mostly same as above] +
|Dec 4 22:16:06 tita kernel: ppp: channel ppp0 closing.
|Dec 4 22:16:06 tita kernel: ppp0 released
|Dec 4 22:16:06 tita kernel: ppp0: ccp closed
|Dec 4 22:16:06 tita pppd[274]: LCP: timeout sending Config-Requests
|Dec 4 22:16:06 tita pppd[274]: Connection terminated.
|Dec 4 22:16:06 tita pppd[274]: Receive serial link is not 8-bit clean:
|Dec 4 22:16:06 tita pppd[274]: Problem: all had bit 7 set to 0
|Dec 4 22:16:07 tita pppd[274]: Exit.
|
|I can connect to my ISP using Win95 with no problem at all. but the
|modem response in Linux is terribly slow, the username> prompt shows
|after 2+ minutes if i tried to log via terminal login, i can only get
|until: `Entring PPP' then it sits there, i press continue button (using
|kppp) and soon the modem hangs.
Don't know much about kppp except that it's a front-end to pppd.
But the "terribly slow" plus what's in the logs strongly suggests that
the wrong IRQ is configured for the device file. Doing "setserial
/dev/ttySx", x=whatever appropriate for your modem, will show what
IRQ is configured.
The IRQ configured for the device file must agree with the IRQ the
modem actually uses, and no other process can use it while pppd
uses it. Check with "cat /proc/interrupts" when the modem is not in
use to see whether the IRQ is used by anything else.
Setserial configures the device file, usually in a boot-up file.
The IRQ that the modem uses may be changed by jumpers, an MS-DOS
program, or by isapnp and pnpdump if it's a PnP modem.
Your option file looked OK, although you might consider removing the
"escape ff" option. It's rarely useful and it can cause trouble
when the ISP PPP implementation isn't up to par.
---
Clifford Kite Not a guru. (tm)
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
