Spontaneous LCP ConfReq after connection made

[James Cameron <james.cameron@hp.com>]

[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

G'day,

pppd tears down a connection and starts a new one, without the modem
hanging up, in response to an LCP ConfReq that arrives out of the blue
from the peer.

I'm thinking it's a peer bug, but I'm not sure, and I can't do anything
about the peer, as it's a consumer service by an apparently
disinterested service provider who refuses to resolve problems if
"unsupported" software is used.

Can anyone suggest anything?

Is there somewhere in pppd source where I can easily disable this
response, in case I can continue the existing connection?


The debug and dump output is here;
http://quozl.linux.org.au/mm-5100/2005-08-12/rtt-fail.log
(the SIGHUP after the restart is generated by my ip-down script)

The pppdump output is here;
http://quozl.linux.org.au/mm-5100/2005-08-12/rtt.pppdump

The service I'm using is a CDMA 1x RTT modem attached by USB;
http://quozl.linux.org.au/mm-5100/

pppd is from Debian GNU/Linux sarge, 2.4.3-20050321
Linux kernel 2.6.11.7 on i686.

Problem is reproducible; most easily if there is a PPTP session active
on another interface and packets begin to be sent over the new interface
as a result of a route change, but also during normal operation without
any PPTP session active.  Sometimes it will operate for minutes or
hours, sometimes only seconds.  The trouble always begins with an LCP
ConfReq out of the blue, and generally in apparent response to some
packet sent by my end.

-- 
James Cameron
http://ftp.hp.com.au/sigs/jc/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]