I can't blame them. Everyday you have someone coming up with some issue that the Flint 2 has that is based around the MediaTek drivers. Maybe they will knock it out of the park.
1 Like
I have extremely low faith in their ability to produce quality, stable and secure software. They can't even market their products well-enough. Look at their social media: goofy photos of people holding routers in front of some random scenery with poorly worded descriptions. Or the tech influencers reviewing them, by reading off a spec sheet.
I don't think I'd be interested in this router for free, considering vanilla OpenWrt support is unlikely (I recently gave away all my non-OpenWrt network hardware).
1 Like
it's ipq5322.
Same as the Unifi Express 7, and a few other devices.
So it's based on a 23.05 qualcomm sdk fork of Openwrt.
The Unifi Express 7 has a 10G WAN, this does not.
1 Like
The current urgent uboot upgrade for the mt2500 in their forums bricking mt2500s is worth reading.
My mt2500 is staying on my desk as I've read about 5 or 6 so far being properly bricked from the update.
Still better than Asus then. 
2 Likes
So a fallacy of relative privation 
1 Like
It's still OpenWrt.
It's Qualcomm. It will be supported at some point.
I believe IPQ95xx and IPQ53xx are more friendly as far as upstreaming is concerned i.e. no NSS subsystem, but wouldn't exactly say that it for sure will be supported, especially any time soon.
Off topic - but I'm wondering if that goes back to the mediatek-uboot and arm-trustzone - and the OKD issues with some mediatek AX targets
Chatted offline with a GLInet guy, and they are fixing a specifc set of targets - I specifically asked him about MT6000 and it was not impacted...
1 Like
Yeah - that's interesting - for all their chips, there is QSDK...
What can be ported over - I suppose it depends.
IPQ6000 seems to be clean for the moment, not sure if it has all the sexy NSS stuff, but it's ok for now with that target...
It's still QSDK.
GL.iNET declared the speeds on VPN on flint 3.
at 630mbps on wireguard is about 1/3 slower than the Flint 2. So the SOC is for sure slower.
the only upgrade I see its the wifi7 for whoever need it
2 Likes
Gl-inet sent an email with a survey about the GL-BE9300. I responded to the survey telling them I'm not interesting in a QC device due to relatively poor open source support, and to make a GL-MT6000 sequel using the Filogic 880. I suggest others do the same if they receive said survey 
14 Likes
They’re supposedly partnering to make the OpenWrt Two. So you’ll get your wish.
Feedback is still good for their regular commercial offerings, but ultimately they’re a business who needs to follow new trends and get products out there using whatever chips are available to them at a good price.
9 Likes
Some really questionable design on the Flint 3.
They moved to a slower Qualcomm chip with ACTIVE cooling on top of that.
Slower 2.4Ghz and 5.0Ghz band. The 6.0Ghz band is faster and a welcome addition but not all devices support it. 2x2 on all three bands as opposed to 4x4 on the Flint 2. The 2.5Gb on all ports is a nice improvement but like 6.0Ghz band, it only serves some niche use cases.
It seems to support more VPN protocols but I don't think it's the most asked feature request.
I am tempted to try to get the early bird discount but I don't see any reason to update from my Flint 2.
3 Likes
It's relying on MLO for heavy lifting but that's not found on any WiFi 6 or 6e device.
Hello everyone!
I’m thinking about getting the Flint 3 as a dedicated VR access point. I know that most of today’s headset do not support WiFi 7, but I want to prepare to Valve’s next headset, which is rumored to have WiFi 7 support.
Would it be good for that?
My main concern is that’s I don’t really know if OpenWRT properly supports WiFi 7 or not. But the super early bird discount is really good compared to other WiFi 7 routers (like the ASUS RT-BE92U).
Thanks for the advice in advance!
You read my mind 
How would we know?
It's not supported by OpenWrt right now and won't be for quite some time to come.
If you want the marketing blurb, ask the vendor.
If you care about running OpenWrt, choose among the already supported devices. Buying something now and just hoping for the best is not going to work. In the best of cases you'll have to wait months++ (I would expect at least well over two years at this point) for support to materialize -or not-, it's very well possible that a particular device will never be supported (be it because it's not supportable at all, or because no one got to it (pricing, availability, etc.; there are quite a few very interesting ipq807x devices that could be supported by OpenWrt, but aren't (yet, or ever))).
3 Likes