When is the new beta expected to be released?
2 Likes
It connects to the GND of PCBA，to achieve shielding. not real earth/ground
1 Like
I don’t know, this week maybe? depends on gl’s internal tests. If everything goes well, they can launch this week.
remembering that I am a user like all of you, I am not a staff member and I am not part of gl.inet.
I wish gl.inet staff provided more information about next release, what it should fix, when it should be released.
Not giving enough information makes everyone upset.
And guess what, I am upset now.
Basically, no basic feature works.
2.4GHZ, does not work.
5GHz, does not work.
Wired connection, does no work.
Disconnections, all the time.
This router is the most unreliable one I have ever used. “Tried to use” I should say.
And on top of that we have no clue if these will eventually be fixed.
I did not buy this router as a beta tester, I paid the full price, this is disappointing, upsetting and highly unprofessional.
Do not sell hardware that just does not work.
1 Like
Did you create a dedicated thread about your issues, so someone can walk through the diagnostics and troubleshooting steps with you?
I’m using my Flint2 since it arrived, and it does it job. So it’s not that “no feature works” - some have issues, indeed, but they all work.
1 Like
Not true.
Just having the same SSID for both 2.4 and 5GHz is a problem.
I “kinda” work. But it does not work.
This is far from good enough.
No one, no one, is using it with no problem.
And I am not a beta tester. I am not a power user.
The only things I expect to work flawlessly are routing, wired ethernet, 2.4GHz and 5GHz wifi.
They just don’t.
They are so many glitches that it would take literally months to open an issue for each one of them.
Again, I am not a beta tester.
So I was patiently waiting for a firmware update that would fix it all, but having no ETA on its release made me get upset.
1 Like
PS: Having to reboot it every day allows me to say that nothing works. Because indeed, nothing works until I reboot it. No wifi, no Internet, nothing.
Did you? Because I would say “no”
they don’t work, and the criticism is valid, and he doesn’t need to reinforce what I and many others have already told the devs, so yes, there are problems and no, it doesn’t work as it should, restarting every day is stupid and doesn’t make sense .
Edit: And if it were to be launched with the MINIMAL things of a non-working router, it would be better not to have launched it and wait longer…
And please, don’t come with the fallacy that if you don’t like it, return it… a lot of people bought imports and that possibility doesn’t exist…
4 Likes
to be honest for me it works fine, well for wireless the 2.4ghz im also experiencing issues.
for the ethernet I’m not, though I think its a good idea like @admon suggested to create a new topic.
What I can suggest now:
Can you turn off the switch?, and then restart all your switches in order?
maybe the awnser is just a rogue switch and becomming rogue once the link was down, it’s kinda also a feature for switches to failover to a different port as wan and if you were unlucky and it sent dhcp then basicly its closed off.
one switch can handle it better than the other, I previously had tp-link managed switches and I found them the worst implemented as it can sent vlans the opposite direction and sent source traffic instead of destination traffic which OpenWrt sees as duplicate source traffic.
latests openwrt snapshots seem to have fixed most of the issues (running it -i can say- stable on the only one mt6000 device kept -for testing purposes only- from 3 pre-ordered), apart from 2.4GHz WiFi. why glinet dev team is waiting to release a new firmware based on the latest openwrt snapshots… well, only they know… just got two days ago a redmi ax6000 (same chipset) for testing and router doesn’t have any of the issues of MT6000 (running latest openwrt SNAPSHOT (r24870-ced3fbcda1) and/or latest stable 23.05.2 (r23630-842932a63d) ) so i guess it might be a hardware design flaw with MT6000 (the only valid explanation) WiFi 2.4ghz.
1 Like
You are 100% correct.
I did not open a thread per issue.
First because all the issues I encountered had already been debated.
So IMHO it would really be counterproductive.
Also I must say I really feel uncomfortable with your tone: correct me if I’m wrong but you give me the impression that you think that I am responsible for all the problems I get with this router.
Again, I am no beta tester. I bought this router, I paid full price, I expect it to provide the minimal features, which it does not.
I do not mean to be unpleasant, I really wanted to like this router, but so far the experience has been nothing but pain.
Yes and no. I believe that “crying” on the Internet doesn’t achieve much. Either you come to terms with the situation and make the best of it, or you have to take official channels and send the device back, for example.
Since my device runs reasonably faultlessly and I know others where this is the case, you simply have to ask yourself whether it is a software, hardware or user issue.
2.4 GHz and 5 GHz sometimes have problems. However, neither is “unusable” - especially if you temporarily abandon the 160 MHz band. Of course, this does not correspond to the advertising - but in this case you have to say for yourself “OK, 160 MHz was important to me, I’ll send the device back and never buy anything from GL.iNET again”
If you don’t do this, then you also have to play a part in solving the problem. It’s enough to share your configuration, used devices and logs - simply to help the community and make a solution possible.
@xize11 Said it in more friendly words in the next post. 
2 Likes
I agree with this, but sometimes a issue is not clear and a further diagnose is needed, you want this issue to be resolved correct?, networking can be difficult, and I mean difficult to forsee every possible issue or solution or situation.
one majority says it works, another say it doesn’t, yet everyones topology differiates.
but with only complaining we get nowhere to understand where it comes from, will not help, will not fix the issue but is also not constructive.
thats why I advise strongly to make a new topic 
show some steps how you reproduce it and your topology, and maybe also your config.
it can be a deffective unit, it can be a rogue switch, it can be a bug.
it’s not we say you do it wrong, but its still valid to diagnose it by eliminating possible outcomes, a support help desk also have not always the direct and right awnsers right ? 
, okay it’s a expensive product but sometimes also expensive products can be having issues.
without the reproduction, this cannot be solved.
1 Like
I would separate 2.4 & 5ghz names until they fix issues with same ssid.
When I did that my wifi issues went away.
I have to say I also have an AP (Asus) connected to this one via ethernet. So the load is not all on the router (I have over 50 devices wired + wireless + multiple servers)
Also one thing that helps me , I write down all my settings and when I upgrade firmware, I reset the router and enter those settings again. You can also backup/restore configs after upgrading firmware, but I am not sure how much is backed up.
Bon Courage
p.s @admon is correct , opening separate threads makes sure your issues are not lost here.
1 Like
Excuse me, could you tell me if this Xiaomi redmi ax6000 has 2.5GB Wan and LAN?
I must say, I was VERY disappointed to find the Flint 2 did NOT have shielded RJ45 jacks unlike my Linksys WRT1900ACS which does have shielded RJ45 jacks. Would be very easy to tie everything to earth ground with shielded network cables if the Flint 2 had shielded RJ45 jacks.
This is a issue with the USB 3.0 specification. It can’t be solved except with shielding. I suspect your problem would be solved by using a USB 3.0 stick with a metal case. https://www.amazon.com/Verbatim-Metal-Executive-Flash-Drive/dp/B017JIHKWQ?th=1
1 Like
no 2.5g, only gigabit
Assuming you’ve got fast internet access, while using the Redmi AX6000 would you be able to perform a speed test from a device (e.g. an older laptop or Android phone) that’ll use 802.11n over 2.4GHz at 40MHz? And ideally you should be just a few meters away from the router.
I forgot to mention this, but it turns out the reason I didn’t experience crashes might of been because a different commit was merged and backported to 23.05. So the issue has already been fixed in OpenWrt.
I don’t know if the next GL.iNet firmware will fix the issue though, since even their test firmware isn’t fully in sync with OpenWrt.