My new Flint 2 router is already having problems with it dropping the Internet connection randomly every couple of days. The message in admin is:
"The interface is connected, but the Internet can't be accessed."
Both ethernet and wireless clients cannot access the Internet when this happens. Nobody in my house can use the Internet when this happens. A soft or hard reboot of the router is necessary to re-establish a connection.
Having started into computers in 1978 I'm not a newbie, but I'm not an expert, either. I have spent a couple of hours reading threads on this forum and it seems several others have the same issue since firmware v4.5. Some said reverting to v4.4 makes the problem go away, however I can't download any firmware older than v4.5 (GL.iNet download center). I would love to test to see if v4.4 remedies the problem or not, so I know for sure if the problem is firmware based or not.
The current firmware is v4.6.4. I connect to a residential Rogers cable Internet account with a dynamic IP which is obtained by WAN DHCP. I don't utilize any of the functions found under the VPN or APPLICATIONS tabs. All clients in the house receive dynamic IPs from the LAN DHCP, with a couple of exceptions which are statically addressed with IPs from outside of the DHCP range. The only 'abnormal' thing about my simple network is perhaps the fact I run Pi-Hole & Unbound on a Raspberry PI for my adblocking and recursive DNS.
Fifteen minutes ago I read a post that suggested disabling all 'Interface Status Track' under the Multi-WAN tab, which I went ahead and did disable for Ethernet1, Repeater, Tethering and Ethernet 2.
Nope, it went 8 days then dropped the Internet connection again. Zero indication that the Internet is unavailable on the router. LED is solid, the GUI says it's connected, yet nobody can surf the net and I can't even ping a host like 1.1.1.1. I am not utilizing any of the fancy features of this device, I just want a basic, reliable internet connection.
Time to return this router. The GL.Inet support is among the worst I've seen over my lengthy career. Pity.
I've been having a similar issue for several months.
Background - I'm with start.ca in Ottawa Canada. My previous router (Turris Omnia) was loosing it's internet connection on a regular basis. I wrote a bash script that would reboot the router if it lost internet connection for more than 5 min which it started doing incessantly.
So I took the plunge and invested in a Flint 2.
I've noticed however that I'm periodically getting the same message as the OP. Typically manually rebooting the router restores the connection.
I've contacted start and they seem to see no issues at their end. They sent a technician who also could not see any problems but suggested trying a new modem.
The new modem (and router) have not seemed to fixed the problem. One common factor is that my old Turris and new Flint 2 are both running OpenWRT... is that perhaps the issue?
Anyone have any suggestions? (other than asking the same question in an OpenWRT forum)
Ive kind of the same issue
I live in the Netherlands and we have glass fiber connection. I have like a small box in a room where the internet is coming from, I then setup my Glint MT6000 on PPOE settings.
Once I had this issue and after searching for so long it was my son who actually loosened a cable from that glass fiber box thingy thats up againnst the wall.
So I fixed that.
But now since a couple of days I'm having this issue where the internet is dropping out of the blue, and I don't know why.
I hope it's not the modem/router. As a gamer and home worker I can't have these type of issues.
Im just replying so that this forum page wont die.
Ive just installed the latest firmware version 4.7.0, hopefully that will fix the issue.
It sounds like either you ISP was slow to respond to a DHCP renew request, the request or reply was delayed by the router, or maybe some other more unlikely reason like packet loss or corruption. But under normal circumstances, a DHCP client would not drop the connection during renewal and will attempt renewal at about half the lease TTL to allow plenty of time for issues. Either way, glad it is working.