On Thu, 22 Jul 1999, Simon Hosie wrote:
|Under the good kernel it works but under the bad kernel it doesn't. Things
|don't get past the LCP stage. All that Documents/networking/ppp.txt said
|was to either patch 2.2.0f, or get the latest version, so I got the latest
|version (I can't find 2.2.0f). I've recompiled everything to make sure
|things match up, and that hasn't helped. To me what appears to be the
|significant difference is...
[edited]
|versus this when things don't work (kernel 2.2.10 and the pppd of your choice):
|
| Jul 22 04:32:02 cowpat pppd[219]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
|<magic 0x335a50c7> <pcomp> <accomp>]
| Jul 22 04:32:05 cowpat kernel: ppp: tossing frame (e0)
One tossed frame isn't a problem.
[edited]
|from syslog using kernel 2.2.10 using kdebug 7:
| Jul 22 04:32:05 cowpat pppd[219]: rcvd [LCP ConfReq id=0x0 <asyncmap 0x0>
|<auth pap> <magic 0xef6682a8> <pcomp> <accomp>]
| Jul 22 04:32:05 cowpat pppd[219]: sent [LCP ConfAck id=0x0 <asyncmap 0x0>
|<auth pap> <magic 0xef6682a8> <pcomp> <accomp>]
|
| (where everything after [but not including] the tossed frame is repeated
| every 3 seconds until it gives up)
You are getting the ISP negotiation messages and responding to them. The
ISP doesn't respond at all to your Configure-Ack's. A good guess is that
the UART type configured for /dev/cua2 is not the same type as that of the
actual UART for the serial port used by the modem.
Check the configured UART with "setserial /dev/cua2" and compare it to the
actual type for the serial port. Configuration of the device file is done
by setserial in a resource configuration file at boot-up.
BTW you should be using /dev/ttyS2 rather than /dev/cua2, at some point
the kernel support for /dev/cua* may be removed. But it's still there for
2.2.9 .
---
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]
