OpenWrt 24.10.0-rc5 - Fifth release candidate

Release and security announcements
1

Hi,

The OpenWrt community is proud to announce the fifth release candidate of the upcoming OpenWrt 24.10 stable series.
OpenWrt 24.10.0-rc5 incorporates over 5300 commits since branching the previous OpenWrt 23.05 release and has been under development for over one year.

This is just a release candidate and not the final release yet.

Download firmware images using the OpenWrt Firmware Selector:

Please test this version

This is not the final version, this is a test version. Please report problems and bugs in our issue tracker. https://github.com/openwrt/openwrt/issues

Changes between OpenWrt 24.10.0-rc4 and 24.10.0-rc5

Target changes:

  • ath79: Buffalo WZR-450HP2: Add device
  • ath79: tiny: Save space by using mv88e6060.ko
  • bcm27xx: Add RP1 drivers
  • bcm27xx: Update GPU firmware and utils
  • ipq40xx: Extreme Networks WS-AP3915i: Fix preserving configuration in sysupgrade
  • ipq40xx: Extreme Networks WS-AP3915i: Fix MAC address
  • ipq40xx: FritzBox 7520/7530: Fix MAC address
  • ipq40xx: NETGEAR orbi: Fix MAC address
  • lantiq: xrx200: AVM 5490/5491: add support for lan3 and lan4
  • loongarch64: Activate procd jail support
  • mediatek: OpenEmbed SOM7981: Update to new board revision
  • mediatek: D-Link AQUILA PRO AI M60: Add device
  • mediatek: WSR devices: Fix image verification in sysupgrade
  • mediatek: filogic: Cudy AP3000 v1: Add device
  • mediatek: D-Link AQUILA PRO AI M30 A1: Fix U-Boot variables handling
  • ramips: mt762{0,8}: Fix eMMC / SDCard support
  • ramips: Amped Wireless ALLY: Improve boot
  • realtek: GS1900: Fix compat_version
  • realtek: HPE 1920-24G-PoE-370w: Add device
  • realtek: HPE 1920-24G PoE-180W (JG925A): Add device
  • realtek: trim default package selection
  • rockchip: NanoPC T6: enable USB3 port
  • octeon: Fix USB3

Generic changes:

  • Linux Kernel update to version 6.6.69
  • mac80211: update to version 6.12.6
  • mac80211: rt2x00: improvement stability of rt2800 driver
  • mt76: update to Git HEAD (2025-01-04)
  • yafut: Fix not found package in imagebuilder
  • kmod-nfnetlink-cthelper: Add new package
  • hostapd: add SAE support for wifi-station and optimize PSK file creation
  • mbedtls: Deactivate ARIA block cipher by default

For a detailed list of changes since OpenWrt 24.10.0-rc5 see the 24.10.0-rc5 changelog.

Highlights in OpenWrt 24.10:

General changes

  • TLS 1.3 support in default images
    • mbedtls was updated to version 3.6 which includes support for TLS 1.3
  • Activate POSIX Access Control Lists and file system security attributes for all file systems on devices with big flash sizes. This is needed by docker nowadays.
    • This is activated for all targets which do not have the small_flash feature flag. small_flash is set for the ath79/tiny, bcm47xx/legacy, lantiq/ase, lantiq/xrx200_legacy, lantiq/xway_legacy, ramips/mt76x8, ramips/rt288x, ramips/rt305x and ramips/rt3883 targets.
  • Activate kernel support for Multipath TCP on devices with big flash sizes.
  • Improved support for WiFi6 (802.11ax) and initial support for WiFi7 (802.11be)
    • Not many Wifi7 devices are supported by OpenWrt yet
  • Improved Link Layer Discovery Protocol (LLDP) support
  • OpenWrt 24.10 uses OPKG only, APK packages are not supported. Only main branch was changed to APK.

Many new devices added

OpenWrt 24.10 supports over 1950 devices. Support for over 100 new devices was added in addition to the device support by OpenWrt 23.05.

Target changes

  • Added d1 target for AllWinner D1 RISC-V SoC
  • Added ixp4xx target for Intel XScale IXP4xx SoCs.
  • Added loongarch64 target for SoCs with Loongson LoongArch CPUs.
  • Added starfive target for StarFive JH71x0 (7100/7110) SoCs.
  • Added stm32 target for STMicroelectronics STM32 SoCs.
  • Renamed ipq807x target to qualcommax.
  • Removed ath25 target. It supported Atheros ieee80211g devices with maximum 16MB RAM
  • Removed bcm63xx target. It supported some Broadcom DSL MIPS SoCs and was replaced by the bmips target. The Broadcom DSL itself was never supported.
  • Removed octeontx target. It supported the Octeon-TX CN80XX/CN81XX based boards
  • Removed oxnas target. It supported the PLXTECH/Oxford NAS782x/OX8xx
  • The qoriq target for the NXP QorIQ (PowerPC) SoCs is built
  • The ipq806x target for Qualcomm Atheros IPQ806X SoCs was converted to DSA

Core components update

Core components have the following versions in 24.10.0-rc5:

  • Updated toolchain:
    • musl libc 1.2.5
    • glibc 2.38
    • gcc 13.3.0
    • binutils 2.42
  • Updated Linux kernel
    • 6.6.69 for all targets
  • Network:
    • hostapd master snapshot from September 2024, dnsmasq 2.90, dropbear 2024.86
    • cfg80211/mac80211 from kernel 6.12.6

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.

  • 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.

Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.0-rc5

In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.0-rc5#known_issues

For a detailed list of all changes since 24.10.0-rc4, refer to
https://openwrt.org/releases/24.10/changelog-24.10.0-rc5

To download the 24.10.0-rc5 images, navigate to:
https://downloads.openwrt.org/releases/24.10.0-rc5/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=24.10.0-rc5

As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.

Have fun!

The OpenWrt Community

To stay informed of new OpenWrt releases and security advisories, there
are new channels available:

17 Likes
3

Still seeing this on x86

image
image617Ɨ146 19.7 KB

Appears to be minor build issue not affecting my config.

Has anyone tried owut from rc4 to rc5 using the resizefs option? I saw a couple of posts indicating issues ( specifically with Nano / RP targets )

1 Like
4

Custom build from firmware-selector is not working for x86/64. Even adding only one simple package, such as 'nano' generates an 'init' in error box, but no details / stdout, etc.

image
image510Ɨ405 27.2 KB

2 Likes
5

See Owut: OpenWrt Upgrade Tool - #383 by efahl

1 Like
6

Right, that's just informational and hence the green text telling you that you are not at risk.

Got a pointer to something? If it's the f2fs thing that @goppinath found, it should not cause you any issues in practice (assuming you don't want to resize again after you upgrade), just --rootfs-size 512 or whatever and it should work fine.

(I've been digging through the makefiles and boot scripts today to try to figure out where that partition type is defined, but zero progress so far.)

2 Likes
7

Thanks Eric, yes it was initially that f2fs post to which you referred.
https://forum.openwrt.org/t/owut-openwrt-upgrade-tool/200035/368
I also saw another post from someone in the -rc4 thread with a Nano RP indicating no boot after 24.10-rc5, but there were not any details.

1 Like
8

After a rock solid 14-day uptime on rc4 updated to rc5 tonight on my GL-MT6000. Updated without a hitch lots of added packages, config etc. Thank you devs.

2 Likes
9

Upgraded from rc4 DIR-3040-A1 preserved everything and works perfectly so far. Big thanks :blush:

10

NanoPi R5C updated from RC4 via owut with no issues to report so far.

11

On the NanoPi R4S 4GB Standard Edition, the LAN port disconnects after a reboot.
This issue occurred on RC4 and is happening again on RC5 (I didnā€™t test earlier RC versions).
The only solution is to power-cycle the device.

Replacing the microSD card and the power supply didnā€™t help.

I also have a NanoPi R2S and R3S, and they donā€™t have this issue!

12

Upgraded my Meraki MR42 and MR52 APs to the same revision as RC5 on the 24.10-SNAPSHOT branch and everything looks good, with the exception of the issues below.

There looks to be some LED confusion on both -- no LAN leds available on MR42 and no tricolor LED available on MR52, but I don't think either of these is a new issue (see https://github.com/openwrt/openwrt/issues/15596 and note that the output there from the MR42 didn't have any orange/green LAN LEDs showing as registered).

13

I don't have much free time this month, but am willing to test some devices for the 24.10.0 release.

I've already tested devices for the apm821xx target.

I have at least one supported device for all targets except loongarch64 and stm32. If there is a target that developers feel could use additional testing please reach out to me and I will test the device(s) I have for that target. If I don't hear from anyone I will concentrate on targets that are new for the 24.10 Release (d1, ixp4xx, omap, qoriq, qualcommax, and starfive).

1 Like
14

Upgraded Netgear WAX202 (used as a WDS repeater) succesfully.

2 Likes
15

FriendlyARM NanoPi R4S 1GB not bootableļ¼Œis the official plan not to support ?

16

I've had the same experience with the R4S have been troubleshooting it for a few days then swapped for a OrangePi R1 plus LTS. Now rocking a NanoPi R3S 2GB no eMMC on 24.10.0-rc5 :+1:

17

Compiled and upgraded ASUS RT-AC3200 & 5300 (stickin' to Ethernet though, since all my wireless is handled by four of those TP-Link Deco X90 mesh units.) succesfully

18

I have an R3S 2GB without eMMC. However, Iā€™d like it to be corrected to R4S, as itā€™s my main router.

19

Upgraded a Netgear WNR3700v2 and R6220 from previous rc4.

1 Like
20

Upgraded my R7800 from 23.05.5 using hnyman's instructions:

rename `/etc/config/network`, `/etc/config/system` and `etc/config/sqm` to <filename>.swconfig
Force upgrade while keeping settings

Everything works, and after copying some configs back to the new files I have my exact same config working but with DSA instead of swconfig.

Thanks devs

1 Like