I have 2 FLINT 2.
Same internet provider, both with FTTH and an ONT, 2 different lines in 2 different houses. Since yesterday, they both disconnect from the ONT that connects through WLAN. Rebooting solves it.
How do I troubleshoot it?
Please follow How to get support quickly
I'm in 4.7.0 since mid december.
I use the DNS of my ISP.
It's the same ONT, it's a normal G.PON ONT using a CAT6. It is attached to the WAN 1 port.
Yesterday, the first one, during the afternoon, kept disconnecting from the ONT. It looked like the ethernet cable got disconnected. Disconnecting and putting it back the cable solved it, rebooting solved it too. I thought it was a faulty wire, but today I arrived at work and I got the same exact issue.
EDIT: it happened again and I stayed there looking at it. Rebooting did not help. The Flint made some cycles "resetting" the WAN door without success. After 10 minutes, it just went up again without any intervention.
The ONT always had green LEDs while this was happening, LAN LED too, even though it was not blinking (meaning no data was going through).
Please follow the linked thread and post some more information like a network diagram, settings, logs, etc.
they're two networks. It's nothing fancy, they both are connected to the ONT through WAN1 and have cabled and wireless clients. The provider is the same, and the technology is the same, it's FTTH with G.PON.
There are some port forward rules for both of them and one of them has two subdomains (192.168.8.x and 192.168.0.x). One of them uses adguard, the other doesn't. Both have openvpn servers for remote access that I seldom use.
I'm attaching the logs from both of them.
logread.tar (216.5 KB)
logread (1).tar (169.5 KB)
I have the same problem since two days ago on the same router. Running 4.7.0 OP24. when I login to the router page it shows me my public IP but there's a notice above that says the interface is down or something like that. A simple reboot fixes the problem.
After a couple of days with no episodes (that I'm aware of, at least) it happened again. Here's the log, evwn though it does not say much.
And today, in the other Flint 2...
Fri Jan 31 12:15:31 2025 daemon.info avahi-daemon[5666]: Interface eth1.IPv6 no longer relevant for mDNS.
Fri Jan 31 12:15:31 2025 daemon.info avahi-daemon[5666]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::9683:c4ff:fea6:f098.
Fri Jan 31 12:15:31 2025 daemon.notice netifd: Network device 'eth1' link is down
Fri Jan 31 12:15:31 2025 daemon.err pppd[12121]: error receiving pppoe packet: Network is down
Fri Jan 31 12:15:31 2025 daemon.notice netifd: VLAN 'eth1.100' link is down
Fri Jan 31 12:15:31 2025 daemon.notice netifd: Interface 'wan' has link connectivity loss
Fri Jan 31 12:15:31 2025 daemon.info avahi-daemon[5666]: Withdrawing address record for fe80::9683:c4ff:fea6:f098 on eth1.
Fri Jan 31 12:15:31 2025 daemon.err pppd[12121]: select (waitForPADO): Interrupted system call
Fri Jan 31 12:15:31 2025 daemon.warn pppd[12121]: Timeout waiting for PADO packets
Fri Jan 31 12:15:31 2025 daemon.err pppd[12121]: Unable to complete PPPoE Discovery
Fri Jan 31 12:15:31 2025 daemon.info pppd[12121]: Exit.
Fri Jan 31 12:15:31 2025 daemon.notice netifd: Interface 'wan' is now down
Fri Jan 31 12:15:32 2025 daemon.notice netifd: Interface 'wan' is disabled
Fri Jan 31 12:15:32 2025 kern.info kernel: [267192.988620] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:01] driver [RTL8221B-VB-CG 2.5Gbps PHY]
Fri Jan 31 12:15:32 2025 kern.info kernel: [267192.998275] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/1000base-x link mode
Fri Jan 31 12:15:32 2025 daemon.notice netifd: Interface 'wan' is enabled
Fri Jan 31 12:15:32 2025 user.notice firewall: Reloading firewall due to ifdown of wan ()
Fri Jan 31 12:15:32 2025 authpriv.notice sudo: root : PWD=/ ; USER=root ; GROUP=nonevpn ; COMMAND=/usr/lib/gl_ddns/dynamic_dns_updater.sh -- stop
Fri Jan 31 12:15:32 2025 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Fri Jan 31 12:15:35 2025 kern.info kernel: [267196.453370] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 2.5Gbps/Full - flow control rx/tx
Fri Jan 31 12:15:35 2025 kern.info kernel: [267196.462090] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Fri Jan 31 12:15:35 2025 daemon.notice netifd: Network device 'eth1' link is up
Fri Jan 31 12:15:35 2025 daemon.notice netifd: VLAN 'eth1.100' link is up
Fri Jan 31 12:15:35 2025 daemon.notice netifd: Interface 'wan' has link connectivity
Fri Jan 31 12:15:35 2025 daemon.notice netifd: Interface 'wan' is setting up now
Fri Jan 31 12:15:37 2025 daemon.info avahi-daemon[5666]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::9683:c4ff:fea6:f098.
Fri Jan 31 12:15:37 2025 daemon.info avahi-daemon[5666]: New relevant interface eth1.IPv6 for mDNS.
Fri Jan 31 12:15:37 2025 daemon.info avahi-daemon[5666]: Registering new address record for fe80::9683:c4ff:fea6:f098 on eth1.*.
I'm so sick and tired of gl.inet and their unreliability. Never in 10 years I had these kind of issues with fritzbox.
OpenWRT and managing adguard, VPNs and so on from the router is extra cool but this persistent unreliability is a deal breaker. I'm switching back to the old fritzes and never again I'll buy another gl.inet!!
How did you set up your PPPoE?
using the provider credentials. The ONT is connected to the WAN, I have login and pw and VLAN ID set to 100 and that's it. But bear in mind that I haven't had these issues until 3 days ago, and I have had this exact setup since september and may. Therefore it cannot be a setting issue. They both started acting up at the exact same time so either it's the provider's fault (unlikely) or it's some bug in the flint 2. The flint 1 is in another line with the same provider and always in FTTH with the same ONT and it has not had any problems.
Anyway no issues with the old fritz so far. It's such a shame that glinets are so unreliable.
I have 1 flint v1, 2 flint v2, an E750 and a marble. The amount of time I spent in two years dealing with fw bugs, especially in the flint 2 and in the E750, is more than the time I spent troubleshooting the fritzboxes in 10 years. Awesome functionalities, awesome UI, affordable products but a bunch of wifi pairing issues, overheating and compatibility issues in the E750, and now this. Don't send out new firmware and new products until it's 100% reliable!!