On Tue, 28 Mar 2000, Ivo Simicevic wrote:
|after upgrading from 2.0.38 to 2.2.14 (Debian distibution) and to ppp 2.3.8
|on server I started having problems with ppp.
|Namely, very often I can't reach authorization phase at all, I am getting
|just this :
|Mar 28 15:58:21 ip pppd[1297]: rcvd [LCP ConfReq id=0x2 <asyncmap 0x0>
|<magic 0x662a2a12> <pcomp> <accomp>] Mar 28 15:58:21 ip pppd[1297]: sent
|[LCP ConfAck id=0x2 <asyncmap 0x0> <magic 0x662a2a12> <pcomp> <accomp>]
|Mar 28 15:58:22 ip pppd[1297]: sent [LCP ConfReq id=0x2 <asyncmap 0x0>
|<auth pap> <magic 0xf0d11432> <pcomp> <accomp>] Mar 28 15:58:23 ip
|pppd[1297]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <auth pap> <magic
|0x4563f03d> <pcomp> <accomp>]
It would be nice to have more context, e.g., the ConfAck received in the
last line is not an Ack for the ConfReq sent in the next-to-last line and
timing is often a consideration.
My best guess from what you did post and your narrative is that the IRQ
configured for the device file is not the IRQ that the modem's serial port
actually uses. Doing "setserial /dev/ttySx", x=whatever for the device
file that pppd uses will show what IRQ is configured.
|and it repeats like this forever .
|
|If I somehow get connected, I get local and remote IP address OK but there is
|no flow (i.e. pinging remote IP doesn't work) .
That behavior might well be consistent with configuring the device file
for the wrong IRQ. I deliberately misconfigured an IRQ once just to see if
a connection was possible, which it was, but I don't remember anything
about the on-line behavior - I might have just quit at that point.
If you need to post again then would you please format the post to
approximately 80 columns. Some of us are text challenged that way.
---
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]
