ramips: Hongdian H7920: Fix pin configuration and MAC addresses
Various fixes and improvements
mac80211: ath10k: improve "failed to flush transmit queue" errors
rockchip: rk3399: Fix PCIe
kernel: ksmbd: Fix SMB access from Linux clients
bcm53xx: Fix bootup of devices
Core components update
Linux kernel: update from 6.6.104 to 6.6.110
mac80211: update from 6.12.44 to 6.12.52
odhcpd: update from 2024-05-08 to 2025-10-02
ubus: update from 2025-07-02 to 2025-10-17
mbedtls: update from 3.6.4 to 3.6.5
openssl: update from 3.0.17 to 3.0.18
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the Phicomm K2T, TP-Link Archer C60 v2, TP-Link Archer C60 v3 and possibly others. For details, see issue #14541.
The same seven targets that failed to create working imagebuilders, and hence no ASU containers, for 24.10.3 have also failed for 24.10.4:
at91/sama5
at91/sama7
bcm4908/generic
bmips/bcm63268
bmips/bcm6362
layerscape/armv7
layerscape/armv8_64b
EDIT: As of 2025-10-26, backports to openwrt-24.10 fixed the container builds for the the above targets (thanks, @robimarko!). This means that although they do not have 24.10.4 ASU builders, they are available in 24.10-SNAPSHOT now and will be available in 24.10.5 and later.
Additionally bcm47xx/mips74k is being late to the game, so may or may not get ASU support, we'll see... Yup, it worked, so bcm47xx support is there.
I have tested x86/64, ath79/generic and mediatek/filogic builds using ASU with owut, they build without issue. If you encounter issues with ASU upgrades, please report them on the respective client threads:
EDIT:
An FYI in case anyone is using it, the Netgear WAX218 (qualcommax/ipq807:netgear_wax218) profile is broken in the 24.10.0 through 24.10.4 imagebuilders, so has no ASU support in this release. The regular download images are fine, so you can still do a manual upgrade, but owut, LuCI ASU and Firmware Selector won't help you.
This has been fixed for 24.10-SNAPSHOT and on main snapshot, so all of the ASU clients work for those versions.
You should be "promoted" to be the project's Release Manager. Get all the ducks in a row before the announcements are made, like you did today with the usual ASU files and docker images. Thanks for smoothing things out for the rest of us.
Oh, hell no, this is @hauke's and @aparcar's (and others) domain and there's no way I could do 5% of what they do (everyone should tip their hats to them, for their literal years and years of making this all possible).
Release management is way too much work, I'm just trying to fix target- and build-specific issues and make upgrades simple, clean and reliable for all devices. My philosophy is that keeping things up-to-date is the single most important step you take in device security, so that has become my focus.
Upgraded NanoPi R4SE from 24.10.3 to 24.10.4 without a problem. LAN is now working as expected which wasn’t the case on previous 24.10.x versions. Great work! Thanks a million!
Also updated 2 * Ubiquiti UniFi AC LR without a problem.
Upgraded WRT1900ACS and 3x WSM20 APs from 24.10.3 using Attended Sysupgrade.
All upgraded without errors, but the problem with high CPU use when disabling wireless still exists on the WRT1900ACS, as reported for 24.10.3.
Also, the WRT1900ACS seems to not respect wifi transmit power settings. I tried reducing power in steps down to almost nothing, but my APs’ Channel Analysis do not report any change in received signal. This is true for both 2,4 and 5 GHz.
That is true when your talking device security. However, not every device out there is in an environment where patching a security hole will make it "more secure" than it already is. In this case the only vulnerability this service release patches with wide applicability is the ubusd one and an attacker would have to get root level access to the router in order to get an exploit running on it in which case your already hosed.
It's not clear to me that a stock OpenWRT router connected to the Internet is exploitable from a remote attacker on the Internet with this one, or even a local wifi client has any more ability to get the kind of access needed to exploit it. In fact on thinking about it I'll go out on a limb and say they can't, period.
Succesfully flashed to TP-Link Archer AX80 EU version, yes EU version is possible since yesterday But then, my wifi's go down because mt7986_eeprom_mt7975_dual.bin file in /lib/firmware/mediatek/ directory gets deleted. How to make it permanent?
But then, my wifi's go down because mt7986_eeprom_mt7975_dual.bin file in /lib/firmware/mediatek/ directory gets deleted. How to make it permanent?