OpenWrt 24.10.3 - Service Release

Release and security announcements
61

NWA50AX Pro .2 → .3, no issues.

62

I had the problem with batman-adv on 5 ghz as wifi couldn’t connect to satellite aps. I’m also using WPA3-SAE for mesh backaul.The problem is on gl-mt6000 router ( flint 2). Other dumb aps, linksys 4 of them, doesnt have that problem.

I have installed wpad-openssl instead of basic on all of them.

Edit:

Your router has also mediatek wifi hardware. They changed wireless drivers for mediatek and it seems to me that affected are routers using mediatek wifi drivers and specific encryption, very likely, wpa3/sae.

63

Forgot the feedback:

EdgeRouter-X update went fine using owut

My path:

  1. Rebooted the device (you never know what may linger in a running system)

  2. Ran owut check and got an error

    $ owut check
Runtime error: Unable to dlopen file '/usr/lib/ucode/uloop.so': Error relocating /usr/lib/ucode/uloop.so: uc_vm_exception_object: symbol not found
In /usr/bin/owut, line 10, byte 34:

let PROG    = ${NAME}/${VERSION};
Near here -----------------------^

$

  3. Upgraded ucode packaging (thanks @efahl) to a consistent set.

    opkg update
opkg list_installed \
| awk '/^ucode-mod-/{print $1}' \
| xargs opkg upgrade ucode libucode

  4. Ran owut check again and confirmed that it was working.

  5. Finally ran the upgrade command.

System is up and running for 10+ hours now, no issues.

Thanks guys, the support on this forum has been really great!

1 Like
64

Let me report a successful upgrade of a Netgear WAX202, used as a WDS repeater. Everything worked just like it was before. I like the new HD icons in Luci.

The attempted attended sysupgrade of GL-iNet GL-MT6000 (Flint 2) was unsuccessful: lots of “checksum or size mismatch” errors.

I have not attempted to upgrade TP-Link Archer C7 v2, as an upgrade from 23.05.6 to 24.10.x would introduce a critical regression in sstp-client: https://github.com/openwrt/packages/issues/27318 (duplicate: https://github.com/openwrt/packages/issues/27324). I will try if I figure out (or if anyone hints me) how to build an otherwise-stock image with a custom patched rebuild of sstp-client using the Image Builder.

65

Tried to upgrade my T-56.

root@t56:~# owut check
ASU-Server     https://sysupgrade.openwrt.org
Upstream       https://downloads.openwrt.org
Target         mediatek/filogic
Profile        zyxel_ex5601-t0-ubootmod
Package-arch   aarch64_cortex-a53
Version-from   24.10.2 r28739-d9340319c6 (kernel 6.6.93)
Version-to     24.10.3 r28872-daca7c049b (kernel 6.6.104)
94 packages are out-of-date
It is safe to proceed with an upgrade

So I went with owut upgrade and it failed:

Collected errors:
 * opkg_install_pkg: Checksum or size mismatch for package avahi-dbus-daemon. Either the opkg or the package index are corrupt. Try 'opkg update'.
 * opkg_install_cmd: Cannot install package avahi-dbus-daemon.
 * opkg_install_pkg: Checksum or size mismatch for package avahi-utils. Either the opkg or the package index are corrupt. Try 'opkg update'.
 * opkg_install_cmd: Cannot install package avahi-utils.
 * opkg_install_pkg: Checksum or size mismatch for package libcurl4. Either the opkg or the package index are corrupt. Try 'opkg update'.
 * opkg_install_cmd: Cannot install package ddns-scripts-cloudflare.
make[2]: *** [Makefile:234: package_install] Error 255
make[1]: *** [Makefile:171: _call_manifest] Error 2

Will wait.

UPDATE: problem solved, device upgraded.

1 Like
66

Wi-Fi still don’t work with Linksys E7350 both 24.10.2 and 24.10.3.
Fortunately flashing 24.10.1 sysupgrade image brought Wi-Fi back, again.

67

Zyxel EX5601-T0 (ubootmod): Upgrade via Attended Sysupgrade from 24.10.2 > 24.10.3 went smooth as well!

1 Like
68

My DIR-890L failed to upgrade with attended sysupgrade it stalled at 50% , tried to upgrade with owut and it reported a successful build but it failed to reboot , finally I used the DLINK recovery to load the new OpenWRT version 24.10.3 without success , I had to revert to 24.10.2 . Something in the upgrade broke the comparibility with the DIR-890L. Anybody else with a bcm53xx router having issues ?

69

I’ve successfully updated my Bananapi BPI-R4 using owut and no longer have the lan disco lights.

70

My NanoPi R6S got an update from 24.10.2 to 24.10.3 via Luci / Attended Sysupgrade.

Everything went fine, even the script to extend the ext4 root-partition was executed.

Thank you team :nerd_face:

71

Many thanks.
All units updated using 'owut' (for those on 24.10.2) and Attended System Update (for one on 23.05.5).
Did not take long at all.

72

UPDATE

1 hour later or so … issue fixed !

I keep OP for reference

I started upgrading 24.10.2 to 24.10.3 using sysupgrade followed by install of packages and all went fine but 4 packages cannot be installed on GL-iNet Slate GL-AR750S.

libacl libattr rsync owut

Checksum or size mismatch

I use rsync for backup

opkg install complains for these 4 packages like e.g.

# opkg update
# opkg install libacl
Installing libacl (2.3.2-r2) to root...
Downloading https://downloads.openwrt.org/releases/24.10.3/packages/mips_24kc/packages/libacl_2.3.2-r2_mips_24kc.ipk
Installing libattr (2.5.2-r3) to root...
Downloading https://downloads.openwrt.org/releases/24.10.3/packages/mips_24kc/packages/libattr_2.5.2-r3_mips_24kc.ipk
Collected errors:
opkg_install_pkg: Checksum or size mismatch for package libattr. Either the opkg or the package index are corrupt. Try 'opkg update'.
opkg_install_cmd: Cannot install package libacl.

Will the 24.10.3 mips_24kc packages be corrected or do I need to wait for 24.10.4 ?

I do not have this problem on e.g. GL-iNet Beryl GL-MT3000

73

I reinstalled the factory image and then restored my backup, and now everything is working fine. I have no idea what went wrong, but luckily everything is working again now. Thanks for your help.

74

Yeah, these are a result of running the imagebuilder during a package upgrade, either the package or its index has completed uploading, but the other one hasn't. Then, when ASU fires off the build, opkg sees things in an inconsistent state with the above errors as a result.

As you've found (at least @hrw), waiting a bit for the package builds to finish and retrying is the current solution.

You will also see this occasionally from just a command line opkg update && opkg install something, it's not something ASU is doing. The situation is caused by the frequent rolling package builds.

Just for background, the package build deploys a lot of stuff, for example in https://downloads.openwrt.org/releases/24.10.3/packages/aarch64_cortex-a53/packages/ we've got 4574 files using 2231 MB. (The magic all happens in https://github.com/openwrt/buildbot if some devops wizard wants to take a look and see if they can come up with some ideas.)

2 Likes
75

Upgraded NanoPi R5C gateway (500/20 ISP, CAKE, adblock, multiple VLANs), Netgear GS308T switch and Reyee RG E5 dumb AP’s (several SSID’s for the segregated VLANs) a day ago from 24.10.2 to 24.10.3 with owut. iperf3 confirms WiFi throughput as expected and Gig Ethernet lines routing at line speed.

I did notice a bit of latency spiking (incoming audio ticking) on a video conference last night served over WiFi (4 hour Teams session for a virtual night school class). I had similar issues with a 24.10-SNAPSHOT some weeks ago and backed off to 24.10.2, which resolved the issues during the long video conference sessions. Waveform shows a couple download spikes in the 300-400ms range, but that is such a quick snapshot in time. I’ll stay with 24.10.3 for now and see how it goes. I could be imagining it - the issues are by no means debilitating.

76

No problem building a new image and sysupgrade my ERL3.

#/bin/bash

RELEASE="24.10.3"
TARGET="octeon"
ARCH="generic"
PROFILE="ubnt_edgerouter-lite"

if [ "$RELEASE" = "snapshots" ]; then
    ARCHIVE="openwrt-imagebuilder-$TARGET-$ARCH.Linux-x86_64.tar.zst"
    UPDATE="openwrt-$TARGET-$ARCH-$PROFILE-squashfs-sysupgrade.tar"
    wget https://downloads.openwrt.org/$RELEASE/targets/$TARGET/$ARCH/$ARCHIVE || exit 1
    tar --zstd -xvf $ARCHIVE || exit 2
else
    ARCHIVE="openwrt-imagebuilder-$RELEASE-$TARGET-$ARCH.Linux-x86_64.tar.zst"
    UPDATE="openwrt-$RELEASE-$TARGET-$ARCH-$PROFILE-squashfs-sysupgrade.tar"
    wget https://downloads.openwrt.org/releases/$RELEASE/targets/$TARGET/$ARCH/$ARCHIVE || exit 1
    tar --zstd -xvf $ARCHIVE || exit 2
fi
cd openwrt-imagebuilder-$RELEASE-$TARGET-$ARCH.Linux-x86_64
rm -rfv files
mkdir files
cd files/
tar zxvf /tmp/backup-OpenWrt-*.tar.gz || exit 3
mv -v etc/config/system etc/config/system.swconfig
mv -v etc/config/network etc/config/network.swconfig
cd ..
make image PROFILE="$PROFILE" PACKAGES="mc diffutils lsblk libgcc libustream-mbedtls \
nftables luci uhttpd kmod-fs-vfat dosfstools block-mount luci-i18n-base-fr luci-i18n-firewall-fr \
luci-i18n-package-manager-fr freeswitch-lang-fr luci-mod-dashboard luci-i18n-dashboard-fr \
ethtool-full owut luci-app-attendedsysupgrade luci-i18n-attendedsysupgrade-fr procps-ng \
procps-ng-watch isc-dhcp-client-ipv4 arp-scan luci-i18n-statistics-fr collectd-mod-ping \
rsync file fdisk" FILES="files" || exit 4
cp -v bin/targets/$TARGET/$ARCH/*.tar /tmp/ || exit 5
make clean
rm -v /tmp/backup-OpenWrt-*.tar.gz
cd ..
scp -O /tmp/$UPDATE root@192.168.16.111:/tmp/$UPDATE
sync
rm -v /tmp/$UPDATE

exit 0
77

Upgraded my Fritzbox 4040 (ipq40xx target) from .2 to .3 via owut and all went smoothly.

Hats off to developers and testers!

78

There is an issue with upgrading, both using owut and attended sysupgrade on aarch64 for what looks like a failure in compiling frr:

Downloading file:packages/Packages
Updated list of available packages in /builder/build_dir/target-aarch64_generic_musl/root-rockchip/../../../../builder/dl/imagebuilder
Downloading file:packages/Packages.sig
Signature check passed.
/builder/build_dir/target-aarch64_generic_musl/root-rockchip/etc/init.d/frr: line 21: /usr/sbin/frrcommon.sh: No such file or directory
./etc/init.d/frr: line 21: /usr/sbin/frrcommon.sh: No such file or directory
Pseudo file "dev" exists in source filesystem "/builder/build_dir/target-aarch64_generic_musl/root-rockchip/dev".
Ignoring, exclude it (-e/-ef) to override.
error: ext4_allocate_best_fit_partial: failed to allocate 5 blocks, out of space?
make[3]: *** [/builder/include/image.mk:399: /builder/build_dir/target-aarch64_generic_musl/linux-rockchip_armv8/root.ext4] Error 1
make[2]: *** [Makefile:268: build_image] Error 2
make[1]: *** [Makefile:163: _call_image] Error 2
make: *** [Makefile:337: image] Error 2
79

Just updated MT-6000 by owut from .2 to .3, all good. only ad guard home and watchcat installed, very easy setup

80

Since updating my EdgeRouter-X (ER-X) from 23.05 to 24.10.2 and now to 24.10.3 I notice the following log messages where I have no idea where they are from.

Wed Sep 24 20:38:06 2025 kern.info kernel: [ 1159.161490] br-lan.1: left allmulticast mode
Wed Sep 24 20:38:06 2025 kern.info kernel: [ 1159.170058] br-lan: left allmulticast mode
Wed Sep 24 20:38:06 2025 kern.info kernel: [ 1159.311123] br-lan.1: entered allmulticast mode
Wed Sep 24 20:38:06 2025 kern.info kernel: [ 1159.320244] br-lan: entered allmulticast mode
Wed Sep 24 20:38:06 2025 kern.info kernel: [ 1159.332172] mtk_soc_eth 1e100000.ethernet eth0: left allmulticast mode
Wed Sep 24 20:38:06 2025 kern.info kernel: [ 1159.520968] mtk_soc_eth 1e100000.ethernet eth0: entered allmulticast mode
Wed Sep 24 20:40:32 2025 kern.info kernel: [ 1305.506934] br-lan.1: left allmulticast mode
Wed Sep 24 20:40:32 2025 kern.info kernel: [ 1305.515581] br-lan: left allmulticast mode
Wed Sep 24 20:40:32 2025 kern.info kernel: [ 1305.629290] br-lan.1: entered allmulticast mode
Wed Sep 24 20:40:32 2025 kern.info kernel: [ 1305.638368] br-lan: entered allmulticast mode
Wed Sep 24 20:40:32 2025 kern.info kernel: [ 1305.647885] mtk_soc_eth 1e100000.ethernet eth0: left allmulticast mode
Wed Sep 24 20:40:32 2025 kern.info kernel: [ 1305.798924] mtk_soc_eth 1e100000.ethernet eth0: entered allmulticast mode
Wed Sep 24 20:42:51 2025 kern.info kernel: [ 1444.247353] br-lan.1: left allmulticast mode
Wed Sep 24 20:42:51 2025 kern.info kernel: [ 1444.255910] br-lan: left allmulticast mode
Wed Sep 24 20:42:51 2025 kern.info kernel: [ 1444.366516] br-lan.1: entered allmulticast mode
Wed Sep 24 20:42:51 2025 kern.info kernel: [ 1444.375600] br-lan: entered allmulticast mode
Wed Sep 24 20:42:51 2025 kern.info kernel: [ 1444.385255] mtk_soc_eth 1e100000.ethernet eth0: left allmulticast mode
Wed Sep 24 20:42:51 2025 kern.info kernel: [ 1444.556297] mtk_soc_eth 1e100000.ethernet eth0: entered allmulticast mode
Wed Sep 24 20:44:38 2025 kern.info kernel: [ 1551.721299] br-lan.1: left allmulticast mode
Wed Sep 24 20:44:38 2025 kern.info kernel: [ 1551.730026] br-lan: left allmulticast mode
Wed Sep 24 20:44:38 2025 kern.info kernel: [ 1551.904630] br-lan.1: entered allmulticast mode
Wed Sep 24 20:44:38 2025 kern.info kernel: [ 1551.913702] br-lan: entered allmulticast mode
Wed Sep 24 20:44:38 2025 kern.info kernel: [ 1551.923263] mtk_soc_eth 1e100000.ethernet eth0: left allmulticast mode
Wed Sep 24 20:44:39 2025 kern.info kernel: [ 1552.084332] mtk_soc_eth 1e100000.ethernet eth0: entered allmulticast mode

I am aware of that EEE issue on the MT7621 (https://github.com/openwrt/openwrt/issues/17351), but that is resolved since 24.10.2 so should not be related.

I also found another thread ( Repeated logs for entered/left allmulticast mode - #10 by nicolas314 ) where they just installed and configured igmpproxy (but I’m not aware of using multicast at all in my network).

Any ideas?