From: Guillaume Nault <gnault@redhat.com>
To: linux-ppp@vger.kernel.org
Subject: Re: PPPoE Modem hangup after random time - how to debug?
Date: Mon, 04 May 2020 18:11:59 +0000 [thread overview]
Message-ID: <20200504181159.GA7717@pc-3.home> (raw)
In-Reply-To: <CAPJ9Yc8Wvxb_UoqGu=wrrWX2HP5AwE98jvcS3XYnvevxa0RZpg@mail.gmail.com>
On Mon, May 04, 2020 at 06:36:48PM +0200, David Balažic wrote:
> On Mon, 4 May 2020 at 15:01, Guillaume Nault <gnault@redhat.com> wrote:
> > You can use "%pM" for printing MAC addresses. Also, it'd be interesting
> > to have information about promisc mode:
> > "dev %s, flags: %#x, promiscuity %u",
> > dev->name, dev->flags, dev->promiscuity,
>
> "ifdown wan" triggers a PADT response from the server, and then this
> code prints:
>
> dev eth1.3902, flags: 0x1003, promiscuity 0
>
I'm not sure what "ifdown wan" is supposed to do. Assuming "wan" is the
name of your ppp interface (wasn't it "pppoe-wan" in your previous
logs?) and that ifdown works like on Debian, then it makes sense that
the peer disconnects the PPPoE session by sending a PADT. At least now
the device isn't in promisc mode.
> I'll report later values printed when a stray PADT appears.
>
Okay, but please keep printing the destination MAC address of the
packet. I was providing the flags/promiscuity string just to get extra
information, not to replace your original log.
Also, what's the driver of your NIC (ethtool -i eth1)?
> Regards,
> David
>
next prev parent reply other threads:[~2020-05-04 18:11 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
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 [this message]
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=20200504181159.GA7717@pc-3.home \
--to=gnault@redhat.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).