I went ahead and made my own OpenWRT build with 24.10.5 for the Flint 2. It is running great and very stable with IPv6, Wireguard, Adguard Home and a bunch of other stuff. You cannot dirty flash from 24.10.5 to 25.12 rc2 as WIFI will not work (data structure?). But the 24.10.5 works great.
I would love to test as well
I am using 25.12rc2 on 3 of my ln1301 (Linksys) but wanted to keep my flint2 with glui, maybe I’ll have to go the pure openwrt way too.
Ive flashed 24.10.5 → 25.12 rc2 on my Linksys and it works flawlessly.
Dirty or clean flash? I may do a dirty flash without WIFI data. Or remove WIFI data after a dirty flash and rebuild that part. I am trying to avoid full router setup from scratch.
Dirty
If I am understanding correctly, your Linksys router flashed fine. I can flash from 24.10.5 to 25.12 rc2 with my Flint 2, but if I retain settings the WIFI does not work on either band. Tried deleting the config for WIFI just rebuilding the WIFI config but that did not work. There appears to be at least an issue with WIFI if you dirty flash from 24.10.5 to 25.12 rc2 on Flint 2.
Maybe an issue specific to flint2, haven’t tried yet.
Yes it looks like it is specific to the Filogic 830 chipset. Various posts on the OpenWRT forum outline issues with radios not starting up, DFS channels not working and issues with country code on 25.12 rc2. The build 24.10.5 is very stable on Flint 2 and the wireless performance is good. For me, I will keep running my own OpenWRT build on the 24.10.5 and wait until 25.12 stable release or when there are a bunch of commits fixing the wireless issues. @Bruce for 25.12 the WIFI scripts change from shell to ucode, a good change for OpenWRT but may have some bugs in the beginning. What is GL.iNet up to with migrating to the newer OpenWRT builds?
The R&D guys is working this. Please wait the release.
I made my own 25.12 rc3 builds. Due to the change to ucode, the vanilla OpenWRT builds do not seem to work with a dirty flash. So I deleted /etc/config/wireless and then flashed the 25.12 rc3 build over my 24.10.5 build. When it booted up, the system created the new wireless config file and I only needed to reconfigure wireless settings not my entire router. Anyway, this is what I did to be able to get from 24.10.5 to 25.12 rc3. Hope this can help someone else.
For vanilla OpenWrt you can also use wifi config to regenerate the configuration.
Though on GL firmware I don't recommend this command, since GL-iNet uses their own script to do wireless especially on the MTK SDK, but also on the OP24 firmwares which is in /rom/etc/uci-defaults.
Otherwise you get a OpenWrt ssid rather than the factory ssid and password ![]()
It looks like with this upgrade from op24 to op25 we might not be able to check "keep settings" ![]()
Won’t be a problem for those who tinker so much anyways.
Can we upgrade without keeping settings and then load the previous settings after a restart?
It just backup in LuCI and then restore the backup after the upgrade?
I'll give it a shot once the firmware is released.
Hi bruce,
Any news on the next OP24 release? I recall seeing a post about a month ago where OP24 needed a fix if your ISP updated your public IP address (many ISPs in my country do this). A workaround was supplied at the time by adding a command as root in the flint2.
Hoping your R&D guys are almost ready to push an update as I can see lots of updates being pushed in the snapshot releases.
The op24 firmware is not our mainline release, so this series updates will be a bit slower.
We are working on adapting the op25 rc, but now we have some issues and the R&D team is still working hard on them.
Which problem are you experiencing on op24-4.8.3?
Please, do not waste your time using an RC version as a base reference.
Skip also the 25.12.0.
Start working on it when it’s more stable, like after the 25.12.1
It should be!! , ops drivers been ready for prime time for a while, y’all just waisting time and resources….
Of course this little rant it just my opinion and I'm going to keep using my router regardless ![]()
Also the question hasn’t been answered yet why there was talk of op24/25/snapshots, which have gone very quiet. This has been asked here and in another thread.