Flint2 - Completely unstable PPPoE

Technical Support for Routers
1

I face a very strange issue with my Flint 2 which started in the last few days, but I only noticed it today since I cannot work. The PPPoE on my Flint 2 disconnects completely randomly, even in less that 10 seconds uptime!

I have tried the previous versions of the firmware, or even the Beta. Nothing fixed it! Even this post took me a lot of time to write it due to the disconnections!

The log file (after a reboot) has the following entries:

Wed Mar 27 21:37:37 2024 daemon.info pppd[11912]: PPP session is 1
Wed Mar 27 21:37:37 2024 daemon.warn pppd[11912]: Connected to XX:YY:ZZ:XX:YY:ZZ via interface eth1
Wed Mar 27 21:37:37 2024 kern.info kernel: [  109.620622] pppoe-wan: renamed from ppp0
Wed Mar 27 21:37:37 2024 daemon.info pppd[11912]: Renamed interface ppp0 to pppoe-wan
Wed Mar 27 21:37:37 2024 daemon.info pppd[11912]: Using interface pppoe-wan
Wed Mar 27 21:37:37 2024 daemon.notice pppd[11912]: Connect: pppoe-wan <--> eth1
Wed Mar 27 21:37:41 2024 daemon.notice pppd[11912]: PAP authentication succeeded
Wed Mar 27 21:37:41 2024 daemon.notice pppd[11912]: peer from calling number XX:YY:ZZ:XX:YY:ZZ authorized
Wed Mar 27 21:37:44 2024 daemon.notice pppd[11912]: local  IP address 1.2.3.4
Wed Mar 27 21:37:44 2024 daemon.info avahi-daemon[5999]: Joining mDNS multicast group on interface pppoe-wan.IPv4 with address 1.2.3.4.
Wed Mar 27 21:37:44 2024 daemon.notice pppd[11912]: remote IP address 5.6.7.8
Wed Mar 27 21:37:44 2024 daemon.notice pppd[11912]: primary   DNS address 10.10.10.10
Wed Mar 27 21:37:44 2024 daemon.info avahi-daemon[5999]: New relevant interface pppoe-wan.IPv4 for mDNS.
Wed Mar 27 21:37:44 2024 daemon.info avahi-daemon[5999]: Registering new address record for 1.2.3.4 on pppoe-wan.IPv4.
Wed Mar 27 21:37:44 2024 daemon.notice netifd: Network device 'pppoe-wan' link is up
Wed Mar 27 21:37:44 2024 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Wed Mar 27 21:37:51 2024 daemon.info pppd[11912]: No response to 5 echo-requests
Wed Mar 27 21:37:51 2024 daemon.notice pppd[11912]: Serial link appears to be disconnected.
Wed Mar 27 21:37:51 2024 daemon.info pppd[11912]: Connect time 0.2 minutes.
Wed Mar 27 21:37:51 2024 daemon.info pppd[11912]: Sent 113878 bytes, received 89466 bytes.
Wed Mar 27 21:37:51 2024 daemon.info avahi-daemon[5999]: Interface pppoe-wan.IPv4 no longer relevant for mDNS.
Wed Mar 27 21:37:51 2024 daemon.info avahi-daemon[5999]: Leaving mDNS multicast group on interface pppoe-wan.IPv4 with address 1.2.3.4.
Wed Mar 27 21:37:51 2024 daemon.info avahi-daemon[5999]: Withdrawing address record for 1.2.3.4 on pppoe-wan.
Wed Mar 27 21:37:51 2024 daemon.notice netifd: Network device 'pppoe-wan' link is down
Wed Mar 27 21:37:54 2024 daemon.notice pppd[11912]: Connection terminated.
Wed Mar 27 21:37:54 2024 daemon.info pppd[11912]: Sent PADT
Wed Mar 27 21:37:54 2024 daemon.info pppd[11912]: Exit.
Wed Mar 27 21:37:58 2024 daemon.err insmod: module is already loaded - ppp_generic
Wed Mar 27 21:37:58 2024 daemon.err insmod: module is already loaded - pppox
Wed Mar 27 21:37:58 2024 daemon.err insmod: module is already loaded - pppoe
Wed Mar 27 21:37:58 2024 daemon.info pppd[14012]: Plugin rp-pppoe.so loaded.
Wed Mar 27 21:37:58 2024 daemon.info pppd[14012]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Wed Mar 27 21:37:58 2024 daemon.notice pppd[14012]: pppd 2.4.8 started by root, uid 0
Wed Mar 27 21:38:05 2024 daemon.info pppd[14012]: PPP session is 1
Wed Mar 27 21:38:05 2024 daemon.warn pppd[14012]: Connected to XX:YY:ZZ:XX:YY:ZZ via interface eth1
Wed Mar 27 21:38:05 2024 kern.info kernel: [  137.596007] pppoe-wan: renamed from ppp0
Wed Mar 27 21:38:05 2024 daemon.info pppd[14012]: Renamed interface ppp0 to pppoe-wan
Wed Mar 27 21:38:05 2024 daemon.info pppd[14012]: Using interface pppoe-wan
Wed Mar 27 21:38:05 2024 daemon.notice pppd[14012]: Connect: pppoe-wan <--> eth1
Wed Mar 27 21:38:06 2024 daemon.notice pppd[14012]: PAP authentication succeeded
Wed Mar 27 21:38:06 2024 daemon.notice pppd[14012]: peer from calling number XX:YY:ZZ:XX:YY:ZZ authorized
Wed Mar 27 21:38:07 2024 daemon.notice pppd[14012]: local  IP address 1.2.3.4
Wed Mar 27 21:38:07 2024 daemon.notice pppd[14012]: remote IP address 5.6.7.8
Wed Mar 27 21:38:07 2024 daemon.notice pppd[14012]: primary   DNS address 10.10.10.10
Wed Mar 27 21:38:07 2024 daemon.info avahi-daemon[5999]: Joining mDNS multicast group on interface pppoe-wan.IPv4 with address 1.2.3.4.
Wed Mar 27 21:38:07 2024 daemon.info avahi-daemon[5999]: New relevant interface pppoe-wan.IPv4 for mDNS.
Wed Mar 27 21:38:07 2024 daemon.info avahi-daemon[5999]: Registering new address record for 1.2.3.4 on pppoe-wan.IPv4.
Wed Mar 27 21:38:07 2024 daemon.notice netifd: Network device 'pppoe-wan' link is up
Wed Mar 27 21:38:07 2024 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Wed Mar 27 21:39:45 2024 daemon.info pppd[14012]: No response to 5 echo-requests
Wed Mar 27 21:39:45 2024 daemon.notice pppd[14012]: Serial link appears to be disconnected.
Wed Mar 27 21:39:45 2024 daemon.info pppd[14012]: Connect time 0.5 minutes.
Wed Mar 27 21:39:45 2024 daemon.info pppd[14012]: Sent 472754 bytes, received 443175 bytes.
Wed Mar 27 21:39:45 2024 daemon.info avahi-daemon[5999]: Interface pppoe-wan.IPv4 no longer relevant for mDNS.
Wed Mar 27 21:39:45 2024 daemon.info avahi-daemon[5999]: Leaving mDNS multicast group on interface pppoe-wan.IPv4 with address XXXXXXX
Wed Mar 27 21:39:45 2024 daemon.notice netifd: Network device 'pppoe-wan' link is down
Wed Mar 27 21:39:45 2024 daemon.info avahi-daemon[5999]: Withdrawing address record for 1.2.3.4 on pppoe-wan.
Wed Mar 27 21:39:45 2024 daemon.notice pppd[14012]: Connection terminated.
Wed Mar 27 21:39:45 2024 daemon.info pppd[14012]: Sent PADT
Wed Mar 27 21:39:45 2024 daemon.info pppd[14012]: Exit.
Wed Mar 27 21:39:49 2024 daemon.err insmod: module is already loaded - ppp_generic
Wed Mar 27 21:39:49 2024 daemon.err insmod: module is already loaded - pppox
Wed Mar 27 21:39:49 2024 daemon.err insmod: module is already loaded - pppoe
Wed Mar 27 21:39:49 2024 daemon.info pppd[15680]: Plugin rp-pppoe.so loaded.
Wed Mar 27 21:39:49 2024 daemon.info pppd[15680]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Wed Mar 27 21:39:49 2024 daemon.notice pppd[15680]: pppd 2.4.8 started by root, uid 0
Wed Mar 27 21:40:04 2024 daemon.warn pppd[15680]: Timeout waiting for PADO packets
Wed Mar 27 21:40:04 2024 daemon.err pppd[15680]: Unable to complete PPPoE Discovery
Wed Mar 27 21:40:04 2024 daemon.info pppd[15680]: Exit.
Wed Mar 27 21:40:07 2024 daemon.err insmod: module is already loaded - ppp_generic
Wed Mar 27 21:40:07 2024 daemon.err insmod: module is already loaded - pppox
Wed Mar 27 21:40:07 2024 daemon.err insmod: module is already loaded - pppoe
Wed Mar 27 21:40:07 2024 daemon.info pppd[16303]: Plugin rp-pppoe.so loaded.
Wed Mar 27 21:40:07 2024 daemon.info pppd[16303]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Wed Mar 27 21:40:08 2024 daemon.notice pppd[16303]: pppd 2.4.8 started by root, uid 0
Wed Mar 27 21:40:14 2024 daemon.info pppd[16303]: PPP session is 1
Wed Mar 27 21:40:14 2024 daemon.warn pppd[16303]: Connected to XXXXXX via interface eth1
Wed Mar 27 21:40:14 2024 kern.info kernel: [  197.008622] pppoe-wan: renamed from ppp0
Wed Mar 27 21:40:14 2024 daemon.info pppd[16303]: Renamed interface ppp0 to pppoe-wan
Wed Mar 27 21:40:14 2024 daemon.info pppd[16303]: Using interface pppoe-wan
Wed Mar 27 21:40:14 2024 daemon.notice pppd[16303]: Connect: pppoe-wan <--> eth1
Wed Mar 27 21:40:15 2024 daemon.notice pppd[16303]: PAP authentication succeeded
Wed Mar 27 21:40:15 2024 daemon.notice pppd[16303]: peer from calling number XXXXX:D7:10 authorized
Wed Mar 27 21:40:18 2024 daemon.notice pppd[16303]: local  IP address XXXXXX
Wed Mar 27 21:40:18 2024 daemon.info avahi-daemon[5999]: Joining mDNS multicast group on interface pppoe-wan.IPv4 with address XXXXXXX
Wed Mar 27 21:40:18 2024 daemon.notice pppd[16303]: remote IP address XXXXXX
Wed Mar 27 21:40:18 2024 daemon.notice pppd[16303]: primary   DNS address XXXXXXX
Wed Mar 27 21:40:18 2024 daemon.info avahi-daemon[5999]: New relevant interface pppoe-wan.IPv4 for mDNS.
Wed Mar 27 21:40:18 2024 daemon.info avahi-daemon[5999]: Registering new address record for 1.2.3.4 on pppoe-wan.IPv4.
Wed Mar 27 21:40:18 2024 daemon.notice netifd: Network device 'pppoe-wan' link is up
Wed Mar 27 21:40:18 2024 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Wed Mar 27 21:40:37 2024 daemon.info pppd[16303]: No response to 5 echo-requests
Wed Mar 27 21:40:37 2024 daemon.notice pppd[16303]: Serial link appears to be disconnected.
Wed Mar 27 21:40:37 2024 daemon.info pppd[16303]: Connect time 0.3 minutes.
Wed Mar 27 21:40:37 2024 daemon.info pppd[16303]: Sent 265753 bytes, received 169943 bytes.
Wed Mar 27 21:40:37 2024 daemon.info avahi-daemon[5999]: Interface pppoe-wan.IPv4 no longer relevant for mDNS.
Wed Mar 27 21:40:37 2024 daemon.info avahi-daemon[5999]: Leaving mDNS multicast group on interface pppoe-wan.IPv4 with address XXXXXXX.
Wed Mar 27 21:40:37 2024 daemon.notice netifd: Network device 'pppoe-wan' link is down
Wed Mar 27 21:40:37 2024 daemon.info avahi-daemon[5999]: Withdrawing address record for 1.2.3.4 on pppoe-wan.
Wed Mar 27 21:40:40 2024 daemon.notice pppd[16303]: Connection terminated.
Wed Mar 27 21:40:40 2024 daemon.info pppd[16303]: Sent PADT
Wed Mar 27 21:40:40 2024 daemon.info pppd[16303]: Exit.
Wed Mar 27 21:40:44 2024 daemon.err insmod: module is already loaded - ppp_generic
Wed Mar 27 21:40:44 2024 daemon.err insmod: module is already loaded - pppox
Wed Mar 27 21:40:44 2024 daemon.err insmod: module is already loaded - pppoe
Wed Mar 27 21:40:44 2024 daemon.info pppd[17961]: Plugin rp-pppoe.so loaded.
Wed Mar 27 21:40:44 2024 daemon.info pppd[17961]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Wed Mar 27 21:40:44 2024 daemon.notice pppd[17961]: pppd 2.4.8 started by root, uid 0
Wed Mar 27 21:40:51 2024 daemon.info pppd[17961]: PPP session is 1
Wed Mar 27 21:40:51 2024 daemon.warn pppd[17961]: Connected to XXXXX:b4:d7:10 via interface eth1
Wed Mar 27 21:40:51 2024 kern.info kernel: [  233.610566] pppoe-wan: renamed from ppp0
Wed Mar 27 21:40:51 2024 daemon.info pppd[17961]: Renamed interface ppp0 to pppoe-wan
Wed Mar 27 21:40:51 2024 daemon.info pppd[17961]: Using interface pppoe-wan
Wed Mar 27 21:40:51 2024 daemon.notice pppd[17961]: Connect: pppoe-wan <--> eth1
Wed Mar 27 21:40:52 2024 daemon.notice pppd[17961]: PAP authentication succeeded
Wed Mar 27 21:40:52 2024 daemon.notice pppd[17961]: peer from calling number XXXXXX:B4:D7:10 authorized
Wed Mar 27 21:40:52 2024 daemon.notice pppd[17961]: local  IP address XXXXXXX
Wed Mar 27 21:40:52 2024 daemon.notice pppd[17961]: remote IP address XXXXXX
Wed Mar 27 21:40:52 2024 daemon.info avahi-daemon[5999]: Joining mDNS multicast group on interface pppoe-wan.IPv4 with address XXXXXX
Wed Mar 27 21:40:52 2024 daemon.notice pppd[17961]: primary   DNS address XXXXXXXXX
Wed Mar 27 21:40:52 2024 daemon.info avahi-daemon[5999]: New relevant interface pppoe-wan.IPv4 for mDNS.
Wed Mar 27 21:40:52 2024 daemon.info avahi-daemon[5999]: Registering new address record for 1.2.3.4 on pppoe-wan.IPv4.
Wed Mar 27 21:40:52 2024 daemon.notice netifd: Network device 'pppoe-wan' link is up
Wed Mar 27 21:40:52 2024 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)

Any help would be appreciated

2

The mDNS thingy confuses me. What kind of modem do you use?

3

Connection is fiber like this:

ONT <--> ISP Router (Internet Pass-through/Bridge) <--> MT-6000 <--> LAN
                   ^
                   |----> VoIP

According to them, I had a lot of disconnections in the last few days, however I never noticed. Today, it’s unbearable. Right now I have connected my laptop directly to the ISP router and use PPPoE connection. Without a single issue. So, something strange is happening on the Flint 2.

However, I haven’t changed my configuration for days, last change I did was a factory reset and then I just uploaded my custom TLS certificate and configured the DHCP leases.

And mDNS is not from the external network, it’s from the Flint…

4

increased the LCP echo failure threshold to 500 with the LCP echo interval = 5 seconds and the connection now seems stable.

Google is your best troubleshooting friend !

1 Like
5

I have already seen this article. However, as you can clearly see, this is quite old.

Now, in my case PPPoE is not stable due to a combination of problematic ONT (that ISP will replace soon) and something else. Using my old TP Link router I had way less disconnections, once every hour or so.

Then, I looked at the ppp script since it made no sense that even when I was changing things, pppd was disconnected exactly after 5 attempts!

And the ppp script (/lib/netifd/proto/ppp.sh has the following entry:

[ "$lcp_interval" != "$keepalive" ] || lcp_interval=5

So, in order to make things better for me, I had to set the lcp_interval and the keepalive at the same values. However, it looked that it didn’t work.
Eventually, I completely remove the keepalive option and now things are way better.

The relevant entry is:

       proto_run_command "$config" /usr/sbin/pppd \
                nodetach ipparam "$config" \
                ifname "$pppname" \
                ${localip:+$localip:} \
                ${ipv6:++ipv6} \
                ${autoipv6:+set AUTOIPV6=1} \
                ${ip6table:+set IP6TABLE=$ip6table} \
                ${peerdns:+set PEERDNS=$peerdns} \
                nodefaultroute \
                usepeerdns \
                $demand $persist maxfail $maxfail \
                ${holdoff:+holdoff "$holdoff"} \
                ${username:+user "$username" password "$password"} \
                ${connect:+connect "$connect"} \
                ${disconnect:+disconnect "$disconnect"} \
                ip-up-script /lib/netifd/ppp-up \
                ${ipv6:+ipv6-up-script /lib/netifd/ppp6-up} \
                ip-down-script /lib/netifd/ppp-down \
                ${ipv6:+ipv6-down-script /lib/netifd/ppp-down} \
                ${mtu:+mtu $mtu mru $mtu} \
                "$@" $pppd_options

In any case, I plan to investigate it a bit further as soon as I have proper hardware again.

6

Even if it is old, has it helped you to get a stable connection? Or at least pin point the troublesome value?

7

It was a typo :smiley: I wanted to say odd.
And yes, it help a bit. Currently my fiber is broken, so the connection quality is poor. And removing this line at least doesn’t disconnect me!