Flint 2

To be honest I wanted to stay as much with GL.iNets own custom builds due to simplified setup through GL.iNet UI. Case in point, i've got both the Flint 2 and Beryl AX. With Beryl AX, i'm staying with GL.iNets own builds since this is meant for travel use and tinkering with different setups and conf

All of the „Flints“ ship with „Openwrt“, just that they all are with „GL.iNet“ flavour+closed source drivers. In short, most purists on here and the forums shout that it isn't „Openwrt“, because it uses closed source software/drivers, but compared to other vendors, „GL.iNet“ allows full stock roster

it's available as of April 21st... running firmware v4.9 beta on my Beryl AX takes a lot of memory, +80% just my Adguard Home and no dpi. went back to the stable release, v4.8.1.. DPI in GL-net routers could be useful. but for those with lower ram, stability is the priority. I guess that's why DPI w

At current prices the Flint 2 is $89 (68%) more expensive than what I paid for the BE230, and it doesn't to Wifi 7.Plus, I've had good success with TP-Link for many years but have never heard of GL.iNet. I'm sure it will do fine for those who have one.

Just head to the GL.iNet forum and see the multiple posts with the various issues documented with poor WiFi performance, MLO problems, PPPoE disconnects and port speed negotiation issues. It is widely accepted by users that it has been a poor downgrade from the Flint 2.

No! Specifically for Wi-Fi 7, GL.iNet is actually the worst 'way to go for OpenWrt'. Their Wi-Fi 7 router is Broadcom based, and doesn't run OpenWrt. Meanwhile the Flint 2 was originally released with a Mediatek OpenWrt fork, but they switched to OpenWrt without Mediatek specific vendor patches for