Sane here,
wifi disconnects on 5ghz on roaming between few rooms.
Stock config.
Rolled back to 4.5.4
Modem USB cannot change IP lange range, so your router need change IP lan range.
And yes manual turn on eth2
I went back to 4.5.2 which is stable for me, on 4.5.4 I have a problem with the WiFi disconnecting and then I can no longer connect just by restarting the router.
As Huawei is also uing 192.168.8.1, so please change IP address of either Huawei or MT6000 to others e.g. 192.168.10.1
Hi everyone…or bought the Flint2 at the pre-sale.
Since this morning something very strange has happened, I can’t connect to either the wi-fi or the ethernet network.
The thing that amazes me the most is that I can’t even reset it… it doesn’t work. I tried 10 sec, 30 sec and even a minute.
I also opened a topic to see if anyone can help me
1 Like
Perfect … thankyou so much
@terzuyuspa You should learn how to read. Also grow up.
2 Likes
@opensukk
- That’s not a direct quote from dsouza. You added
"and GL.iNET Flint 2 (GL-MT6000)". - The patch doesn’t do anything to improve 2.4GHz (802.11n), which is what you were originally told.
- The issue you’re referencing mainly affects Apple devices, which is why the screenshots show an iPhone and jkdf2 said that the issue affects his wifes MacBook Pro, while all of his other devices are “perfectly fine”.
You keep creating accounts and posting about this, but it doesn’t change the fact that you’re wrong 
2 Likes
We don’t need any childish behavior here. I have now flagged the comments as “inappropriate”.By virtue of my position as super trustworthy seal, the comments will then be automatically hidden. Magic! 
And now back to the actual topic, please.
From my point of view, blindly patting around won’t help anyway, we’ll have to be patient until the GL team finds a solution (or the problem)
5 Likes
It seems like the mods already banned one of the accounts, so thanks for the reports.
Because OpenWrt is open source there’s always going to be comparisons and people suggesting patches from similar hardware, but I’d encourage others to only post about a potential fix if they fully understand what it does or they’ve personally tested the fix on the GL-MT6000.
As noted, the GL.iNet developers are already aware of the issues. We’ve just got to give them a little time to figure things out.
4 Likes
Wow, what an annoying guy, have they already banned him?
always with the same thing… stubborn guy.
Geez… I was holding off on testing 4.5.5 beta after reading the comments in this thread. It’s quite sad to see the most active thread on this forum being the bugs in the Flint2 firmware. Thankfully you’ve discovered someone who has multiple accounts and been posting some inaccurate information.
Completely agree with Blackbox, we need to give the devs time to fix the issues of this newly released device. Hopefully enough people will use this beta to give some specific feedback and concise evidence to support it.
I’m loving the using my Flint 2 … the budled adguard home is fantastic to use. Using the Flint has made me realise how much i’ve neglected DNS and security before on my old ASUS.
2 Likes
Thank you … i will try .
I went back to 4.5.2 and there was a problem with the wifi, it didn’t connect to anything this morning, unfortunately… I’m using 4.5.5 release1 which is temporary, It is a router with very good specifications but the firmware is very raw, it would have been better to have waited longer to launch than to launch with so many problems.
2 Likes
I’m really asking myself why these WiFi issues didn’t occur during the beta test.
2 Likes
There are so many devices out there and Wi-Fi is so fu~…ndamental complex, that testing all of this is behind the scope you are trying to achieve. Plus there are different country codes. Plus there are different channels in each region, etc. etc.
Of course, better testing would find those issues. But then the product will cost $500.
2 Likes
Did you release 4.5.5 as stable? Shouldn’t I test more? Here for me, after a while I had disconnection problems across my entire network, but there was nothing strange in the log, it only started working again after restarting.
Hi, dont know if this is the same problem, but I noticed when I was using “WPA2-PSK/WPA3-SAE” as Wi-Fi Security, that I sometimes couldn’t connect with some of the devices. Now I am using “WPA2-PSK” and no connection problems anymore.
you may be on to something 