Slow pages loading, time-outs, no pics after 4.8.2 update GL-MT6000

Anyone else experiencing slow pages loading, time-outs, no pics after 4.8.2 update (up from 4.8.1) on GL-MT6000?
It’s like not every web page, but rather once in 10-15 pages, totally randomly.
Don’t even know how to troubleshoot it. Just wanted to see if someone already made conclusion.

7 Likes

It would appear there is a dns problem Flint 2 MT6000 Rolling back from 4.8.2 to 4.7.7 causing internet outage also rolling back to 4.7.7 will cause configuration issues

1 Like

Ha. Surprisingly I’m in Canada too. My AdGuard Home is turned off, never used it.
Is there a way to go down to 4.8.1?

I've rolled back to 4.7.7 for now, reset the router and reconfigured it. I’m new to the Flint 2 so my config is simple for now, only took me 5 mins to do.

I has quite elaborated config and helped find the bugs in previous releases so my config includes some workarounds…. I will not get away with 5 mins. More like 5 days chasing all these things…

1 Like

Install the 4.8.2 and make a Full Reset with New configuration. See of the Problem existing.

Second Solution:

  • Download the 4.8.2 Firmware
  • Make a Full reset of Flint 2.
  • After all online, login and update the downloaded Firmware 4.8.2
  • Don’t keep settings
  • Configure flint 2 and test min. 3 days.

I hade the experience that my flint was able to get the best WiFi channels after 2-3 days. I use Auto Chanels with 2,4 ghz only 20mhz and 5 ghz with full bandwidth

Exactly the Same problem after upgrading to 4.8.2, I have now reset router to default settings to see if it fixes it.

I have the same issue. Upgraded to 4.8.2 and kept settings. Not using VPN nor adguard, just a very simple setup. Same symptoms as you describe. Tried resetting but didn’t fix issues. Had to roll back to 4.7.7

Maybe need to try again to upgrade without keeping settings, although normally this isn’t required for upgrading, only for downgrading.

On 4.8.2 I have changed DNS settings from Auto to Manual with preset “Google Public DNS” and it looks like problem disappeared. Will need more intense browning to be 100% sure - probably on Mon.

1 Like

Came to see what people were saying about the new 4.8.2 FW update for the Flint 2 before I update.

Easiest decision ever, It seems I will wait for the next release.:laughing:

1 Like

Facing exactly the same issues with the 4.8.2-op24 version of the firmeare installed from fresh with no settings kept and mulitiple factory resets after to no avail. Disappointed.

1 Like

Resetting the router ( not just rebooting) seems to have fixed it for now. I had to enter in my settings again - I have just a basic setup it only took 10 mins or so. I upgraded from 4.7.7 to 4.8.2 fron the GL-inet app on the latest apple ios. It does not offer to save settings so just a straight upgrade. Disappointing that is stuffed my internet up with a straight forward upgrade.

edit: take that back it started happening again! What to do?

2 Likes

The same problem. At first I thought it was the provider's problem, but now it seems clear that the reason is in the firmware. I thought about trying the op24 version, but it seems there will be no difference. The only way out is to roll back to 4.7.7? Has anyone tried 4.8.3-snapshot?

Downgrading firmware WITHOUT keeping settings followed by a full RESET and things are still not working properly unfortunately. Will try a Debrick with Uboot and see!

What to do now? Any suggestion from the team? I’m not gonna downgrade and reset my router only to have the same problem again (as the others have mentioned).

FWIW, I had the same issue when upgrading from 4.7 to 4.8. Factory reset helped fix it completely. I know some people have complicated setups, but it’s the same kind of people who can SSH into the router and export their relevant configs. I wouldn’t overwrite any of the config files, just add your stuff on top (I only migrated static DHCP assignments and firewall rules). It doesn’t excuse the post-upgrade mess when you keep the settings, but it’s a solution.

1 Like

Thanks. Looks like factory reset worked. I will edit this post in a few days if problem comes back.

edit: yeah, it doesnt work.

2 Likes

I think this significantly reduced the issue. This definitely makes huge difference.

I run my own dns server so I use custom option. Its the same with other public dns servers, encrypted dns or automatic.

I disabled network acceleration and atm everything works. :crossed_fingers:

Rollback to 4.7.7 and archive backup appeared to have fixed it for now. Has anyone fixed 4.8.2 yet by just tweaking DNS settings? I had default install and was using provider DNS (Automatic)