public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Retallack, Mark \(Siemens\)" <mark.retallack@siemens.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] FW: Ppp echo request problem
Date: Thu, 19 May 2005 14:20:00 -0000	[thread overview]
Message-ID: <B573B0465A4EFB42997BADDC2FBDE154256228@ples506a.stcl.siemens.co.uk> (raw)


We have had a problem with the ppp echo requests, when the ppp
connection has been running for a long period of time.  If the ppp peer
connection is re-negotiated, then the lcp layer can start sending extra
echo requests. The number of requests sent increases each time the
connection is re-negotiated, eventually causing the connection to
terminate automatically after one minute.

The problem seems to be in lcp.c, function LcpEchoCheck. The link can be
terminated during the call to LcpSendEchoRequest if the peer is not
responding and this will result in the timeout being created for the
link which is now closed. When the ppp is re-negotiated, the extra
timeout still persists and causing the problems described above.

Has anyone had this problem?

Suggested fix would be to only call TIMEOUT if the ppp link is still
open - see below:-

static void
LcpEchoCheck (f)
    fsm *f;
{
    LcpSendEchoRequest (f);

    /*
     * Start the timer for the next interval, provided that the
     * link is still in the "OPENED" state.
     */
    assert (lcp_echo_timer_running==0);
    if (f->state == OPENED) {
        TIMEOUT (LcpEchoTimeout, f, lcp_echo_interval);
        lcp_echo_timer_running = 1;
    }
}


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

                 reply	other threads:[~2005-05-19 12:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B573B0465A4EFB42997BADDC2FBDE154256228@ples506a.stcl.siemens.co.uk \
    --to=mark.retallack@siemens.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).