archive mirror
 help / color / mirror / Atom feed
From: Patrick Mahan <>
Subject: PPP cycling between UP and DOWN
Date: Wed, 27 May 2020 19:16:07 +0000	[thread overview]
Message-ID: <> (raw)

PPP v2.3.11
RP-PPPOE v3.12
Linux 2.6.35

I am seeing some issues with respect to how PPP is handling a PPPoE connection.

My PPPoE connection gets established and pppd reports UP via the ip-up script. 
Then at some point (sometimes within a second, sometimes hours) pppd reports down 
via the ip-down script, but does not exit then re-establishes the UP state and 
reports it via ip-up.

I have a script that monitors by this by having a modified ip-up and ip-down 
script write a value to a specific file under /var/run/pppd/ and if it is 
ip-down, then I schedule a restart of pppd to occur once the pppd image exits.  I 
have assumed that ip-down being triggered is and indication that PPPoE connection 
is down and over.

But I am now seeing that this assumption could be incorrect.  I don't claim to 
understand the entire protocol layers involved.  But is it supported that a PPPoE 
connection can shift back from the IPCP layer to the LCP layer?  Then back?

Or is this a ppp protocol issue.  I see in the pppd code that we can moved to a 
down state if we get a request to restart negotiations, so I can see that my 
assumption may be incorrect.

Any help is appreciated.



             reply	other threads:[~2020-05-27 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 19:16 Patrick Mahan [this message]
2020-05-28 13:59 ` PPP cycling between UP and DOWN James Carlson
2020-05-28 17:54 ` Patrick Mahan
2020-06-08 17:04 ` Patrick Mahan
2020-06-08 17:15 ` James Carlson
2020-06-08 21:32 ` David Balažic
2020-06-08 22:51 ` Patrick Mahan
2020-06-08 22:52 ` Patrick Mahan
2020-06-09 18:03 ` James Carlson

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:

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

  git send-email \ \ \ \

* 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 NNTP newsgroup(s).