Thank for the info. I will a bit before upgrading to 25.x
Ah, got it. That was a bug in the version compare code, you've got a newer version of owut now in which that's fixed. Thanks for the details.
Is it safe to force the upgrade in this case with owut?
root@OpenWrt-AP:~# owut check --version-to 25.12.2
ASU-Server https://sysupgrade.openwrt.org
Upstream https://downloads.openwrt.org
Target mediatek/mt7622
Profile xiaomi_redmi-router-ax6s
Package-arch aarch64_cortex-a53
Version-from 24.10.6 r29141-81be8a8869 (kernel 6.6.127)
Version-to 25.12.2 r32802-f505120278 (kernel 6.12.74)
3 packages were downgraded
140 packages are out-of-date
There are 0 missing and 1 modified default packages
WARNING: Checks reveal package downgrades, upgrade still possible with '--force' (re-run with '--verbose' for details)
verbose reveals these packages are a downgrade:
procd 2026.03.14~c59f2d80-r1 2026.03.13~58eb263d-r1
procd-seccomp 2026.03.14~c59f2d80-r1 2026.03.13~58eb263d-r1
procd-ujail 2026.03.14~c59f2d80-r1 2026.03.13~58eb263d-r1
Perhaps off topic: In the anticipated wake of Claude Mythos Preview, where does the cyber-security of OpenWRT 25.12.x stand? Should we expect increased frequency of security service updates? Do we need to move to the master branch for the latest Linux patches and follow nightly builds? Whatâs the best strategy for the next season?
If there are security issues, the fixes will be backported and the minor version increased e.g to 25.12.3
Yeah, that's fine, the 24.10 version just got the update a day later, and since the package uses CalVer versioning it appears to be newer. Using --force to get to 25.12 will build a self-consistent image, so go for it...
I upgraded TP-Link Archer C6 v3 and Zyxel WSM20 from 24.10.x to 25.12.2 with owut, both are dumb APs.
Everything worked flawlessly.
A big thank you
to all contributors.
Installed it on my NanoPi R4S enterprise (LAN-router, without WiFi) and on 2 * Ubiquiti Unifi AC-LR (dumb AP). Online now for 5 days without any issue.
Just upgraded an Asus RT-AX53U from 24.10.5 to 25.12.2.
So far everything looks good.
After 14 das of using this release on Flint 2 the internet speed got realy low (20mbts - fast.com), noticed my IPTV hanging, disabled SQM did no change at all, checked logs nothing. After a reboot all back to normal (500mbts - fast.com) with or without SQM enabled. Also experiencing some IoT devices disconnects with packet loss over wifi.
EDIT: The second issue I am having with mutiple devices (Filogic based) that are running this same release they are:
- 6 x Cudy AP3000 V1
- 1 x Zyxel NWA50AX Pro
- 1 x Cudy AP3000 Outdoor
All of those above run as APâs therefore no SQM running on them to report.
Anyone else with those issues? Had none of those on 24.10.5.
14 day uptime on 25.12.2 on one of my GL-MT6000s. No issues, speed is the best it's ever been.
@JonSnow I encountered the same issue when first upgrading from 24.10.5 to 25.12.0. It is likely due to the default DUID behavior change in the 25.12.0. mmg proposed a fix here. Essentially you need to manually edit the /lib/netifd/proto/dhcp.sh file to restore the default DUID behavior in 24.10.5. I was able to fix it using this approach in both 25.12.0 and 25.12.2
You can try DUID reset on main gateway:
Then reboot ISP gateway and your AP's. Might fix the issues.
Just updated GL.iNet GL-MT6000, thanks a lot!
My ISP provides me with /56 IPv6 and never noticed an issue with it (until 25.10.0 where I couldnât get IPv6 lease from ISP but got that sorted installing some missing packages).