Hi guys, have this router about 3 years now and never a problem, after updating to 4.11.0, it just looses connection for about 30 seconds, i have external router zte mc7010 5g which is in bridge mode and flint 2 is in router mode, did try to do a factory reset on all devices but nothing changes, can you help me pls.
First isolate whether the interruption is on the Flint 2’s LAN/Wi‑Fi side or its WAN/upstream side. From a wired computer, keep these running in separate terminals until the next outage:
- Ping the Flint 2:
ping -t 192.168.8.1 - Ping an Internet IP:
ping -t 1.1.1.1 - If the ZTE management address is reachable, ping that address as well.
Please report which ping fails during the 30-second interruption and whether wired and Wi‑Fi devices are affected simultaneously. If 192.168.8.1 continues responding but both the ZTE and 1.1.1.1 fail, the next step is to examine the Ethernet link/upstream modem; if only 1.1.1.1 fails, we should check the Flint 2 WAN lease and routing. This test avoids assuming that firmware 4.11.0 is the cause based only on timing.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
there was about 3 interuptions on 192.168.8.1, 1.1.1.1 there was only one interuption, none on 192.168.254.1
Please confirm whether all three pings were run simultaneously from the same wired computer. The counts alone cannot correlate the interruptions.
If they were simultaneous, the ZTE remaining reachable while 192.168.8.1 missed replies suggests that not every missed gateway ping represents a WAN outage. For the next event, run ping -t 192.168.8.1 from one wired device and one Wi‑Fi device at the same time. If only Wi‑Fi loses replies, investigate the wireless link; if both lose replies simultaneously, check System → Log immediately afterward and share only the redacted entries covering that timestamp.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
i did notice something, if iptv from my isp provider is working and i start looking at some short clips from insta or facebook then conection is lost on all devices
This points to an interaction with the IPTV traffic rather than a random WAN interruption. Please clarify one topology detail: is the IPTV set-top box connected to the Flint 2 or directly to the ZTE, and have you configured an IPTV VLAN on the Flint 2? This determines whether to investigate multicast/IPTV handling on the Flint 2 or congestion upstream.
Also reproduce it once from a wired client while simultaneously pinging 192.168.8.1, 192.168.254.1, and 1.1.1.1. If the Flint 2 gateway stops responding under this combined traffic while the ZTE remains reachable, export System → Log immediately afterward and share only the redacted section covering the interruption.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
IPTV set-top box is connected to the Flint 2, it’s plug n play, but like i said, it was working fine b4 last update, no issues at all.How do i upload the logs?
In the Flint 2 admin panel, go to System → Log, then click Export (usually in the upper-right corner). Save the downloaded file, remove any sensitive information if present, and attach the file to your forum reply using the paperclip/upload button or by dragging it into the reply editor. Please do not post passwords, tokens, MAC addresses, public IP addresses, or a full configuration backup.
Before exporting, reproduce the interruption once if possible and note the exact time. The timestamp will help identify the relevant entries. If the export option is unavailable, a redacted excerpt covering the interruption is also useful. The IPTV box being connected to the Flint 2 means the next investigation should focus on how the IPTV traffic affects the router, although this does not yet confirm that 4.11.0 is the cause.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
Wed Oct 7 21:26:21 2026 daemon.info dnsproxy[20175]: 2026/10/07 19:26:21.104365 ERROR response received addr=tls://one.one.one.one:853 proto=tcp status="reading response from tls://one.one.one.one:853: read tcp 10.:56690->1.0.0.1:853: i/o timeout"
Wed Oct 7 21:26:57 2026 daemon.info dnsproxy[20175]: 2026/10/07 19:26:57.542162 ERROR response received addr=tls://one.one.one.one:853 proto=tcp status="reading response from tls://one.one.one.one:853: read tcp 10.:43092->1.0.0.1:853: i/o timeout"
Wed Oct 7 21:27:10 2026 daemon.notice netifd: wan (21021): udhcpc: sending renew to 10.
Wed Oct 7 21:27:10 2026 daemon.notice netifd: wan (21021): udhcpc: lease of 10. obtained, lease time 122
Wed Oct 7 21:27:11 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
These entries show two DNS-over-TLS requests to Cloudflare timing out, but the WAN DHCP renewal succeeded one second later with the same address. There is no WAN link-down event in this excerpt, so it may be a DNS interruption rather than a complete connection loss.
Temporarily go to Network → DNS, disable encrypted DNS/DNS-over-TLS, and use Automatic DNS or plain manual DNS (1.1.1.1 and 1.0.0.1). Then repeat the IPTV-plus-video test. If the interruption disappears, the issue is isolated to the encrypted DNS path. If it continues, please post the redacted log from about one minute before through one minute after the exact event, especially any netifd, kernel, mtk, eth, or kmwan entries.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
Is this MAC issue:
un Oct 11 17:45:55 2026 kern.warn kernel: [156339] IN=br-lan OUT= MAC=94:83:33:77::db:ff:6a:2:00 SRC=192.1 DST=192.16 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=119 DF PROTO=ICMP TYPE=8 CODE=0 ID=3 SEQ=1
Sun Oct 11 17:46:32 2026 daemon.notice netifd: wan (24403): udhcpc: sending renew to 10.8
Sun Oct 11 17:46:32 2026 daemon.notice netifd: wan (24403): udhcpc: lease of 10.8 obtained, lease time 122
Sun Oct 11 17:46:32 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Sun Oct 11 17:47:33 2026 daemon.notice netifd: wan (24403): udhcpc: sending renew to 10.8
Sun Oct 11 17:47:33 2026 daemon.notice netifd: wan (24403): udhcpc: lease of 10.86 obtained, lease time 122
Sun Oct 11 17:47:33 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Sun Oct 11 17:48:34 2026 daemon.notice netifd: wan (24403): udhcpc: sending renew to 10.8
Sun Oct 11 17:48:34 2026 daemon.notice netifd: wan (24403): udhcpc: lease of 10.8 obtained, lease time 122
Sun Oct 11 17:48:34 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Sun Oct 11 17:49:36 2026 daemon.notice netifd: wan (24403): udhcpc: sending renew to 10.8
Sun Oct 11 17:49:36 2026 daemon.notice netifd: wan (24403): udhcpc: lease of 10.8 obtained, lease time 122
Sun Oct 11 17:49:36 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Sun Oct 11 17:50:37 2026 daemon.notice netifd: wan (24403): udhcpc: sending renew to 10.8
Sun Oct 11 17:50:37 2026 daemon.notice netifd: wan (24403): udhcpc: lease of 10.806 obtained, lease time 122
Sun Oct 11 17:50:37 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Sun Oct 11 17:50:56 2026 kern.warn kernel: [15991.362115] IN=br-lan OUT= MAC=94:83::a4::77:40::db::6a:28:08: SRC=192.1 DST=192.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=27528 DF PROTO=ICMP TYPE=8 CODE=0 ID=623 SEQ=1
Sun Oct 11 17:51:38 2026 daemon.notice netifd: wan (24403): udhcpc: sending renew to 10.80.1
Sun Oct 11 17:51:38 2026 daemon.notice netifd: wan (24403): udhcpc: lease of 10.80.1 obtained, lease time 122
Sun Oct 11 17:51:38 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Sun Oct 11 17:52:39 2026 daemon.notice netifd: wan (24403): udhcpc: sending renew to 10.80.
Sun Oct 11 17:52:39 2026 daemon.notice netifd: wan (24403): udhcpc: lease of 10.80. obtained, lease time 122
Sun Oct 11 17:52:39 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Hi,
Thank you for the additional information.
If the issue happens again, please SSH into route and run:
ifstatus wan
Please also export the system log after the connection loss occurs and send it to us via private message.
Also, could you please let us know how the IPTV service is connected in your network?
Thank you for your support and understanding.
How to SSH Log in to the Router:
Hi all, I have the same problem. WAN (and VPN) drops out for a couple of minutes.
I try a fresh upgrade and factory reset. Latest stable firmware 4.11.0 (no beta).
I went back to 4.9.1 so will test and see
Edit:I did notice that status led flashes every now and then to blue.
4.9.1 fix you issue?
Nope, still drops connection
Hi,
Sorry for the delayed reply, and thank you for sharing the system logs.
We found several entries showing eth1: Link is Down, followed by the link coming back up at 2.5 Gbps and the WAN interface reconnecting. However, no other anomalies related to this were found in the logs.
Could you please try replacing the Ethernet cable between the ZTE MC7010 and the Flint2? If the issue persists, could you also try using another Ethernet port on the Flint 2 as the WAN port, if convenient?
Regarding the disconnection when watching Instagram or Facebook short videos, could you please let us know which device you use (e.g., a phone, tablet, or computer), and whether it connects to the Flint 2 via Wi-Fi or Ethernet?
Can the issue be consistently reproduced when IPTV and short videos are playing simultaneously?
If the issue occurs, please note the approximate time, export the system log again, and send it to us via private message.
Thank you for your patience and assistance.
Hi,
Are the WAN and VPN disconnections still occurring after the firmware reinstallation and factory reset?
Could you please provide the following information so that we can further verify the situation?
- When the issue occurs, do devices connected via both Ethernet and Wi-Fi lose their Internet connection, or are only certain devices affected?
- During the interruption, do you notice any changes in the Flint 2's indicator LEDs? Can you still access the router's Web Admin Panel?
- Does the WAN connection recover automatically after a few minutes? Does the VPN reconnect at the same time, or does it require a manual reconnection?
If the issue is still occurring, could you please export the system log after the next occurrence and send it to us via private message.
Thank you for your patience and assistance.