From: "David Balažic" <xerces9@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: Re: PPPoE Modem hangup after random time - how to debug?
Date: Thu, 23 Apr 2020 11:12:48 +0000 [thread overview]
Message-ID: <CAPJ9Yc_JEuDV4yEjhyJp-+bo7fkYcFrW58vypqZzAyjRFcuvoA@mail.gmail.com> (raw)
In-Reply-To: <CAPJ9Yc8Wvxb_UoqGu=wrrWX2HP5AwE98jvcS3XYnvevxa0RZpg@mail.gmail.com>
One more thing I noticed:
the packet count for eth1 is much higher than for eth1.3902:
eth1 Link encap:Ethernet HWaddr C4:XX:XX:XX:XX:ED
inet6 addr: fe80::c6xx:xxff:fexx:xxed/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:23147175 errors:0 dropped:0 overruns:3 frame:0
TX packets:12334230 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3553425618 (3.3 GiB) TX bytes:4237688514 (3.9 GiB)
Interrupt:5
eth1.3902 Link encap:Ethernet HWaddr C4:XX:XX:XX:XX:ED
inet6 addr: fe80::c6xx:xxff:fexx:xxed/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:682037 errors:0 dropped:0 overruns:0 frame:0
TX packets:91218 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:373700490 (356.3 MiB) TX bytes:26176360 (24.9 MiB)
As if the eth1.3902 is somehow reset every now and then. I'll keep my eye on it.
Also: the IPv6 address (the part derived from hwaddr) starts with c6
instead of c4 like the actual hw address. Is that normal?
On Thu, 23 Apr 2020 at 12:37, David Balažic <xerces9@gmail.com> wrote:
>
> Some more info:
>
> - the connect time is random:
> # logread | grep "Connect time"
> Wed Apr 22 16:42:18 2020 daemon.info pppd[7960]: Connect time 1742.8 minutes.
> Wed Apr 22 19:13:03 2020 daemon.info pppd[9563]: Connect time 150.7 minutes.
> Thu Apr 23 09:38:31 2020 daemon.info pppd[9884]: Connect time 865.5 minutes.
>
>
>
> - the assigned IP address is different on each connection
>
>
> - logs
> On Thu, 23 Apr 2020 at 00:00, James Carlson <carlsonj@workingcode.com> wrote:
> >
> > 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.
>
> Nothing there:
>
> Thu Apr 23 08:59:02 2020 daemon.info hostapd: wlan0: STA
> 58:XX:XX:XX:XX:b9 IEEE 802.11: deauthenticated due to inactivity
> (timer DEAUTH/REMOVE)
> Thu Apr 23 09:38:31 2020 daemon.notice pppd[9884]: Modem hangup
>
> I'll try packet capture next.
>
> Regards,
> David
next prev parent reply other threads:[~2020-04-23 11:12 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 [this message]
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=CAPJ9Yc_JEuDV4yEjhyJp-+bo7fkYcFrW58vypqZzAyjRFcuvoA@mail.gmail.com \
--to=xerces9@gmail.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).