linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: PPPoE Modem hangup after random time - how to debug?
Date: Wed, 22 Apr 2020 22:00:52 +0000	[thread overview]
Message-ID: <e1ab31e7-66a2-5bd8-1b95-27fa65d0974c@workingcode.com> (raw)
In-Reply-To: <CAPJ9Yc8Wvxb_UoqGu=wrrWX2HP5AwE98jvcS3XYnvevxa0RZpg@mail.gmail.com>

On 2020-04-22 13:45, David Balažic wrote:
> Hi!
> 
> I have a router running openwrt connected to a GPON ONT, running a
> PPPoE connection (hw details below).

This looks to be (possibly) a PPPoE failure, though there's nothing
interesting in the log messages provided.  If there were an interesting
log message, it would almost certainly come somewhere (perhaps even
*minutes*) before that initial "Modem hangup" message.

The definitive test would be to run a packet capture on the Ethernet
interface itself (*not* on the PPP interface) with something like
Wireshark and determine what happens in the lead-up to the failure.  I'd
expect the system is just getting a stray PADT from the peer, if it's
some kind of PPPoE problem.

If it isn't, then possibly it's something else.  I think that the last
time I looked at the PPPoE implementation on Linux it was a bit hokey --
it ran PPP over a pty pair and then decoded the framing in user space
and wrote it back out over Ethernet using PPPoE.  I hope it's not still
like that, as I haven't looked at it in years, but it may well be.  An
internal error in that logic could also cause a "hangup" message,
although hopefully along with some kind of system log about a core file
as well.

(The implementation on other platforms, such as Solaris, was a bit more
solid.)

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

  parent reply	other threads:[~2020-04-22 22:00 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 17:45 PPPoE Modem hangup after random time - how to debug? David Balažic
2020-04-22 19:51 ` Michael Richardson
2020-04-22 22:00 ` James Carlson [this message]
2020-04-23  0:08 ` Guillaume Nault
2020-04-23  0:41 ` Michael Richardson
2020-04-23  2:01 ` James Carlson
2020-04-23 10:37 ` David Balažic
2020-04-23 11:12 ` David Balažic
2020-04-23 12:13 ` David Balažic
2020-04-23 15:59 ` Michael Richardson
2020-04-23 16:01 ` Michael Richardson
2020-04-24 13:47 ` David Balažic
2020-04-24 14:02 ` David Balažic
2020-04-24 14:26 ` James Carlson
2020-04-24 15:44 ` Guillaume Nault
2020-04-24 15:54 ` Guillaume Nault
2020-04-26  1:38 ` Michael Richardson
2020-04-26 12:44 ` David Balažic
2020-04-26 12:48 ` David Balažic
2020-04-26 19:03 ` David Balažic
2020-04-27  2:14 ` Michael Richardson
2020-04-27  9:59 ` David Balažic
2020-04-27 13:43 ` James Carlson
2020-04-27 20:08 ` Guillaume Nault
2020-04-27 20:30 ` Guillaume Nault
2020-04-27 23:34 ` David Balažic
2020-04-28 10:18 ` David Balažic
2020-04-28 11:00 ` Guillaume Nault
2020-04-29 11:58 ` David Balažic
2020-05-03 10:31 ` David Balažic
2020-05-04 12:27 ` Guillaume Nault
2020-05-04 13:01 ` Guillaume Nault
2020-05-04 15:54 ` David Balažic
2020-05-04 16:36 ` David Balažic
2020-05-04 18:11 ` Guillaume Nault
2020-05-04 18:43 ` David Balažic
2020-05-06  9:52 ` David Balažic
2020-05-06 10:34 ` David Balažic
2020-05-06 14:26 ` Guillaume Nault
2020-05-06 15:02 ` Guillaume Nault
2020-05-06 15:15 ` James Carlson
2020-05-06 15:39 ` David Balažic
2020-05-06 15:54 ` David Balažic
2020-05-06 20:20 ` Guillaume Nault

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=e1ab31e7-66a2-5bd8-1b95-27fa65d0974c@workingcode.com \
    --to=carlsonj@workingcode.com \
    --cc=linux-ppp@vger.kernel.org \
    /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 NNTP newsgroup(s).