Good day, Joshua,

On Fri, 26 Jun 1998, Joshua Heling wrote:

> I have a persistent problem at a site that's masquerading a 5-node 
> LAN through a linux box running 2.0.34 with ppp 2.2.0f and an 
> external ISDN TA.
> 
> The connection is established just fine, and works.  However, when 
> used from one of the inside machines, it will work for a short 
> amount of time (<5 minutes; usually only 1-2 min.) and then dies 
> with:
> 
> Jun 25 16:03:45 foo pppd[1713]: Excessive lack of response to LCP 
> echo frames.
> Jun 25 16:03:46 foo pppd[1713]: Hangup (SIGHUP)
> Jun 25 16:03:46 foo pppd[1713]: Modem hangup
> Jun 25 16:03:46 foo pppd[1713]: Connection terminated.
> Jun 25 16:03:46 foo pppd[1713]: Exit.
> 
> [snip]

        The problem is not in ip masquerading, I think.  It's in pppd.
        Your pppd is asking the other end to reply with LCP (link control
protocol) echoes; the lower level equivalent to ICMP pings.  The other end
doesn't respond - this might be a protocol violation, but that's not the
real issue. 
        The way around it is to tell your end to stop asking for lcp
echoes.  From "man ppp":

       lcp-echo-failure n
              If this option is given, pppd will presume the peer
              to be dead if n LCP echo-requests are sent  without
              receiving a valid LCP echo-reply.  If this happens,
              pppd will terminate the connection.   Use  of  this
              option  requires a non-zero value for the lcp-echo-
              interval parameter.  This option  can  be  used  to
              enable pppd to terminate after the physical connec-
              tion has been broken (e.g., the modem has hung  up)
              in situations where no hardware modem control lines
              are available.

       lcp-echo-interval n
              If this option is given,  pppd  will  send  an  LCP
              echo-request  frame  to  the  peer every n seconds.
              Normally the  peer  should  respond  to  the  echo-
              request  by sending an echo-reply.  This option can
              be used with the lcp-echo-failure option to  detect
              that the peer is no longer connected.


        I suspect that putting the following lines into /etc/ppp/options
will stop your problem:

lcp-echo-failure 0
lcp-echo-interval 0

        Best of luck.  Cheers,
        - Bill

---------------------------------------------------------------------------
Unix _is_ user friendly.  It's just very selective about who its friends 
are.  And sometimes even best friends have fights.
William Stearns ([EMAIL PROTECTED])
---------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]

Reply via email to