Hello，
I did not reproduce this issue in v4.8.2 and v4.8.3, and also try enabling and disabling the network acceleration of these 2 versions.
May I know before the firmware update of your Flint2, it was v4.7.x, and after update, it is v4.8.2, right?
Please try to install v4.8.3 (beta) firmware and keep the default configuration (hardware acceleration enabled) to see if there is any improvement.
@bruce if you have a secure upload portal, I’d be glad to send a .tar export of my config (4.8.2 with Hardware acceleration enabled).
Hello,
Thank you for your information!
I will message with you, please check the forum PM.
FWIW, it is definitely happening to my Flint 2 router as well. only way to normalize the issue was to disable network acceleration. I have a fairly simple network setup with a vpn and around 30 devices connected.
Hello,
May I know what firmware version is of your Flint2? If it is v4.8.2, please upgrade to the v4.8.3 beta firmware, enable the hardware acceleration, and check it.
If no luck, please share your router with us via GoodCloud, I would like to remote check your router.
Please PM me your router MAC address and the Admin Panel password.
This beta version has fixed all issues so far, I’ll report back if it happens again but I installed the beta version clean with default settings, only changed to my preferred dns provider, enabled full cone nat, and igmp snooping.
I see 4.8.3 has been promoted to stable for this device - but no mention in the release logs whether it addresses the issue in this thread or not.
Have you checked the log?
https://dl.gl-inet.com/release/router/release/mt6000/4.8.3
It looks like the issue discussed in this thread has been resolved.
Can anyone confirm if this fixes the original hardware acceleration issue? I really don’t want to waste anymore time going back and forward setting things up again..Thank you..
I did/have - the listed points do not relate to this post?
… I was under the impression it was a driver change that caused the problem and a roll back potentially resolved. But that is not mentioned. At all.
I plan to stay on 4.7.7 for now - I prefer the default Kill Switch behaviour in this release as well.
I bit the bullet, early days yet - saved settings upgrade fro 4.7.7. to 4.8.3 stable - Its working so far. 
4.8.2 totally destroyed my online experience with slow web browsing.
And I have a 500/50 fibre connection.
I upgraded to 4.8.3 and re-enabled hardware acceleration, so far so good.
Hello @toString @imimimx
We are very sorry for bringing you a bad experience on version v4.8.2 firmware.
At present, the majority MT6000 users who have upgraded to v4.8.3, report that when hardware acceleration is enabled/selected, the web page access is normal.
If you have any questions, please feel free to let us know, and please prepare for desktop remote access with us to check.
Updated to 4.8.3 and re-enabled Hardware Acceleration - so far so good. Seems to have fixed it.
Well as OP I feel I needed to let ppl know.
Updated to 4.8.3, enabled HW acceleration, also added AdGuard which I did not use before.
2.5 hours in — no issues so far. I’ll update if anything comes up
This is good to know, my work around in 4.8.2 was to disable IPv6 in luci config on LAN interface but now time to update 4.8.3 by the sounds
Where is the transparency on what was changed in 4.8.3 that apparently fixed the problem of 4.8.2?
Has been discussed here; MT6000/Flint2 v4.8.3 stable release - #3 by bruce
Basically a driver fallback to Pre 4.8.2
I did a straight upgrade keeping settings and can confirm after 3 days, 4.8.3 with hardware acceleration is working solid.
I just got this router (MT6000), and immediately started experiencing this issue. It was extremely noticeable, as the issue didn’t exist before installing the router, and went away as soon as I removed the router from the equation. The first time I connected the router to the modem, I upgraded the firmware before doing any setup. I don’t remember what version the firmware was originally, but it upgraded to 4.8.4.
I’m going to give it a couple days of troubleshooting, but it’s looking like I will be returning this router if I can’t find a solution. Separately, I’ve also had issues with SQM. It worked upon initial setup (getting an A+ rating on the waveform bufferbloat test), but after a router reboot, it stopped working.
Quite disappointing.
