Flint 2 - Discussion Thread

Is there a guide to configuring the router (VLAN ID) with stock firmware to connect to Aquiss? I'd like to get this router for when our connection goes live but want to be confident I won't hit a roadblock. I've been searching but getting a bit phased by the results.
 
Is there a guide to configuring the router (VLAN ID) with stock firmware to connect to Aquiss? I'd like to get this router for when our connection goes live but want to be confident I won't hit a roadblock. I've been searching but getting a bit phased by the results.
When you set the router up and set the WAN port to Pppoe (or whatever your provider uses) there is an option there to enter a vlan ID when you enter your username and password
 
Thanks for confirming that, good to know it isn't just me. I also had a quick go with 24.10 openwrt, but that seems to have a bug that disables the 5ghz WiFi if you select 160, dropping to 80 and it comes back on.
24.10.0 although "stable" is still a bit buggy regarding 5ghz on some chipsets (I tried an earlier RC on the MT-6000 and found the 5ghz dropped randomly) and non-functional on others.

The fixes exist upstream though (as evidenced by the Pesa build) so it would be worth checking back after a point release or 2.
 
I bought one of these a couple of months ago, purely so i could have a decent router with customisable SQM QoS. As i game over in a household with on average 16 devices connected, but can be as high as 25-30. So battling with lag is a constant issue, even on a 900Mbps internet connection. All seems to stem from buffer bloat.

What a difference it makes. The fact i can download at 600-700mbps while my son is in a game without it impacting his ability ot play, or vice versa, is game changing compared to any router I've had previously. (Never owned an OpenWRT compatible one previously)

Keeping a close eye on the Flint 3 release because i now want that :D
 
Keeping a close eye on the Flint 3 release because i now want that :D
It's a tricky boat. The Flint 3 is based on Qualcomm which is slightly annoying since if you decide to go Vanilla you then have to decide what wireless driver you want. One has worse performance but is open source and the good performance driver is closed source.

Then again with the issues people have been stating with wireless on the Flint 2, I can't blame them for wanting to try another vendor (Flint 2 is MediaTek based).

Unless the Flint 3 is under $175 I would rather wait for the OpenWRT Two which is being voted on now. If it happens it will be amazing: https://lists.openwrt.org/pipermail/openwrt-devel/2025-February/043722.html

MT7988 (latest MediaTek chip)
10G SFP
5G copper
4 port 2.5G copper
1-2 port 1G copper
Tri-band Wi-Fi 7

All for $250 (should be about £200 delivered in UK). The only thing close to that is the Asus BT8 which only has 2 x 2.5 Gbps ports for £260: https://www.overclockers.co.uk/asus...ri-band-mesh-wifi-7-router-net-asu-03579.html

The BT8 is currently getting OpenWRT support and also has the same MT7988 chip.
 
Last edited:
Then again with the issues people have been stating with wireless on the Flint 2, I can't blame them for wanting to try another vendor (Flint 2 is MediaTek based).
It's a bit of a weird one with the Flint 2, even when I was on the early-ish GL firmware and then on the plain Openwrt, I didn't have too many issues (slow speeds, and I mean not really slow speed on Apple devices, not optimal, but perfectly usable). As mentioned above the GL firmware compared to the Pesa build (albeit a version renowned for it's WiFi stability/performance) is indistinguishable. One is using closed source drivers the other open source.

I've got iPads/iphones/Android/Windows/Linux/ChromeOS/Playstations/Xboxes/VR headsets/smart plugs, including some real cheapo devices all running from mine and trust me if there is a problem I soon hear about it.

The only thing I can think of is there is something going on with power saving on client devices in those problematic cases, but not having had the issue I can't be sure.
 
Last edited:
The only thing I can think of is there is something going on with power saving on client devices in those problematic cases, but not having had the issue I can't be sure.
Yeah I get that. When something gets popular it's hard to know if it's the device or PEBKAC.

Just as an example, some days ago I was looking at some decent mesh points from a brand called Cudy which is also based on OpenWRT. I was reading some reviews and one person was like "Horrible coverage no better than my Vodaphone router" (yes I know it's Vodafone but he typed Vodaphone :P ). Then the picture supplied was the router right at the back at the bottom of a metal shelf.
 
Back
Top Bottom