[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 24.10.1 - Service Release

Hi,
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 24.10 stable series.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org?version=24.10.1
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/24.10.1/targets/
Main changes between OpenWrt 24.10.0 and OpenWrt 24.10.1
Only the main changes are listed below. See changelog-24.10.1 for the full changelog.
Device support
Added new devices:
bmips: Actiontec T1200H
mediatek: CMCC A10
mediatek: Huasifei WH3000
mediatek: Keenetic KN-3811
mediatek: Keenetic KN-3911
mediatek: netis NX31
qualcommax: Linksys MX4300 (LN1301)
ramips: Cudy M1200 v1
ramips: Cudy M1300 v2
ramips: Genexis / Inteno Pulse EX400
ramips: Hongdian H8922 v30
ath79: mikrotik Routerboard 911G: Fix clock speed
ath79: NEC Aterm: Fix initramfs execution
bcm27xx: Raspberry Pi: Fixes for r8169 Ethernet driver
bcm27xx: Raspberry Pi: Update GPU firmware and drivers
imx: Gateworks boards: Misc fixes
mediatek: ASUS: RT-AX59U/TUF-AX4200/TUF-AX6000: Fix boot problems with recent bootloader
mediatek: Xiaomi AX3000t: Fix NMBM handling for devices with Winbond W25N01KVZEIR flash
mediatek: Zyxel EX5601-T0: Fix eth1 wan configuration
ramips: Dovado Tiny AC: Fix wifi MAC addresses
ramips: hiwifi hc5962: Fix reading MAC address
ramips: LAVA LR-25G001: Fix wifi MAC address
ramips: MT7621: Improve MT7621S core detection
ramips: TP-Link Deco M4R v4: Fix port name conflict
realtek: Add new auxiliary MDIO driver and switch devices to it
realtek: HPE 1920: Fix FAN configuration
realtek: Zyxel GS1900-8: Split into v1 and v2
Various fixes and improvements
ath10k-ct: Silence some harmless noisy logs
build: build LLVM toolchain for BPF when packet selects it
dnsmasq: Fix handlers for options filter_rr and cache_rr
kernel: Fix IPv6 TCP GSO segmentation with NAT
kernel: Globally enable CONFIG_PCPU_DEV_REFCNT
kernel: usbnet: Restore usb%d naming for cdc-ethernet devices with local MAC
mac80211: rt2x00: Fix loading EEPROM from card
odhcpd: Fix missed packets in relay mode
umdns: Automatically configure firewall for umdns when needed
Core components update
Update Linux from 6.6.73 to 6.6.86
Update mt76 from 2025-01-14 to 2025-02-14
Update mwlwifi from 2024-04-19 to 2025-02-06
Update wireless-regdb from 2024.10.07 to 2025.02.20
Update ucode from 2024-07-22 to 2025-02-10
Update unetd from 2024-12-17 to 2025-03-09
Update umdns from 2024-09-17 to 2025-02-10
Update omcproxy from 2021-11-04 to 2025-02-27
Update libnl-tiny from 2023-12-05 to 2025-03-19
Update ethtool from 6.10 to 6.11
Update openssl from 3.0.15 to 3.0.16
Update mbedtls from 3.6.2 to 3.6.3
Update ca-certificates from 20240203 to 20241223
Update bcm27xx-gpu-fw from 2024.11.26 to 2025.03.05
Update bcm27xx-utils from 2024.12.19 to 2025.03.14
Update r8125 from 9.014.01 to 9.015.00
Update r8126 from 10.014.01 to 10.015.00
Update r8168 from 8.054.00 to 8.055.00
Update bcm63xx-cfe from 2024-06-25 to 2025-04-02
Update intel-microcode from 20240531 to 20250211
Update firmware-utils from 2024-10-20 to 2025-02-16
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 TP-Link Archer C60 v1, TP-Link Archer C6 v2, and possibly others. For details, see issue #14541.
Ethernet link instability on some MT7530 switches. Users experiencing unstable Ethernet connections should disable Energy-Efficient Ethernet (EEE) as a workaround. See issue #17351 for more information.
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.1
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.1#known_issues
For a detailed list of all changes since 24.10.0, refer to
https://openwrt.org/releases/24.10/changelog-24.10.1
To download the 24.10.1 images, navigate to:
https://downloads.openwrt.org/releases/24.10.1/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=24.10.1
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:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact

4 Replies
24

[Assistant]
Looks like the EX5601/T-56 LED fix didn't make it into the release for some reason. I still have this issue on 24.10.1
github.com/openwrt/openwrt
mediatek: filogic: upstream LEDs control on 2.5G ports on EX5601
main ← abajk:ex5601-phy-led-control
opened
Feb 12, 2025
abajk
+25 -3
This commit switches the control of the leds connected to the Maxlinear GPY211C …
Otherwise everything seems to be working fine with a custom image from the image builder.

AlanDias17:
Oops..
I got the same issue with "GL-MT6000"

2 Replies
3

After a great 67 day uptime on my GL-MT6000 on .0 running lots of added packages/services did a sysupgrade to .1. No issues to note, thanks devs!

7


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 22.03.0-rc1 first release candidate

Hi,
The OpenWrt community is proud to announce the first release candidate of the upcoming OpenWrt 22.03 stable version series. It incorporates over 3400 commits since branching the previous OpenWrt 21.02 release and has been under development for about one year.
This is just a release candidate and not the final release yet.
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/22.03.0-rc1/
Main changes from OpenWrt 21.02:
Firewall4 based on nftables
Firewall4 is used by default instead of firewall3 in the OpenWrt default images. Firewall4 uses nftables instead of iptables to configure the Linux netfilters.
Firewall4 uses the same UCI firewall configuration. Old firewall configurations should still work with firewall4, using nftables now. The extra option which allowed to add custom iptables commands does not work any more.
iptables is not included in the default images any more, it can be added with opkg or ImageBuilder if needed. iptables-nft, arptables-nft, ebtables-nft and xtables-nft provide the known command line interface from the old tools, but they will create nftables entries instead.
Many new devices added
OpenWrt 22.03 supports over 1550 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 21.02. OpenWrt 22.03 supports more than 10 devices capable of Wifi 6 (IEEE 802.11ax) using the MediaTek MT7915 wifi chip.
The qoriq target for the NXP QorIQ (PowerPC) was added in OpenWrt
22.03.
The bmips target for the Boardcom MIPS BCM33xx, BCM63xx and BCM7xxx
SoCs was added.
More targets converted to DSA
The following targets or boards were migrated from swconfig to DSA with OpenWrt 22.03 in addition to the systems already migrated with OpenWrt 21.02:
bcm53xx: All board using this target were converted to DSA
lantiq: All boards using the xrx200 / vr9 SoC
sunxi: Bananapi Lamobo R1 (only sunxi board with switch)
Dark mode in LuCI
The LuCI bootstrap design supports a dark mode. The default design activates dark mode depending on the browser settings. Change it manually at “System” -> “System” -> “Language and Style”.
Year 2038 problem handled
OpenWrt 22.03 uses musl 1.2.x, which changed the time_t type from 32 bit to 64 bit on 32 bit systems, on 64 bit system it was always 64 bit long. When a Unix time stamp is stored in a signed 32 bit integer it will overflow on 19 January 2038. With the change to 64 bit this will happen 292 billion years later. This is a change of the musl libc ABI and needs a recompilation of all user space applications linked against musl libc. For 64 bit systems this was done when the ABI was defined many years ago, the glibc ARC ABI already has a 64 bit time_t.
Core components update
Core components have the following versions in 22.03.0-rc1:
Updated toolchain:
musl libc 1.2.3
glibc 2.34
gcc 11.2.0
binutils 2.37
Updated Linux kernel
5.10.111 for all targets
Network:
hostapd 2.10, dnsmasq 2.86, dropbear 2022.82
cfg80211/mac80211 from kernel 5.15.33
System userland:
busybox 1.35.0
In addition to the listed applications, many others were also updated.
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.0-rc1
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/22.03/notes-22.03.0-rc1#known_issues
For a detailed list of all changes since 21.02, refer to
https://openwrt.org/releases/22.03/changelog-22.03.0-rc1
To download the 22.03.0-rc1 images, navigate to:
https://downloads.openwrt.org/releases/22.03.0-rc1/
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:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at https://openwrt.org/contact

2 Replies
35

[Assistant]
Hi all.
Successfully installed on
Netgear WNR3700v2 (ath79 generic)
Netgear R6220 (mt7621)
x86/64
(more devices to come)
Several devices of each, and various configurations (router, AP, mesh). All working as a charm.
Thank you to everyone who contributed.

4

Successfully installed on
Belkin RT3200 (UBI)
Netgear R7800
TP-Link Archer A7 v5
Thank you, devs.

2

I would like to check out all of them to find one that has support for 802.11ax on both the 5GHz band and the 2.4 GHz band.

2 Replies


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 23.05.5 - Service Release

Hi,
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 23.05 stable series. It improves device support and brings a few bug fixes including security fixes.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=23.05.5
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/23.05.5/targets/
Main changes between OpenWrt 23.05.4 and OpenWrt 23.05.5
Device support
ath25: fix PHY MII settings
ath79: fix PHY MII settings
ath79: GL-AR750: fix I2C pins
ipq40xx: fix PHY MII settings
ipq40xx: Aruba AP-303H: add PoE passthrough GPIO
ipq40xx: Aruba boards: define config-names, fix compatibility with newer apboot revs
ipq40xx: FritzBox 4040: re-add label MAC address
mediatek: CMCC RAX3000M (emmc): improve bootup stability
mediatek: CMCC RAX3000M: fix lan/wan macaddr
mediatek: JDCloud RE-CP-03: improve PHY reset stability
mediatek: UniFi U6 series: fixup models names
mediatek: Zyxel EX5700: add missing 2.5G PHY LEDs configuration
octeon: ubnt-edgerouter: disable PCIe to improve bootup stability
ramips: fix PHY MII settings
ramips: Sercomm NA502s: use lzma-loader
ramips: TP-Link EAP613: bump EAP610-V3 compat_level
realtek: backport VLAN fix
Various fixes and improvements
mac80211: fix wifi throughput regression
Add kmod-r8101, kmod-r8168, kmod-r8125 and kmod-r8126 driver
hostapd: fix SAE H2E security vulnerability
hostapd: fix anqp_3gpp_cell_net list delimiter
lldpd: many improvements
Core components update
Update Linux from 5.15.162 to 5.15.167
Update mac80211 from 6.1.97-1 to 6.1.110-1
Update openssl from 3.0.14 to 3.0.15
Update mbedtls from 2.28.8 to 2.28.9
Upgrading to 23.05.5
Sysupgrade can be used to upgrade a device from 22.03 to 23.05, and configuration will be preserved in most cases.
Sysupgrade from 21.02 to 23.05 is not officially supported.
ipq40xx EA6350v3, EA8300, MR8300 and WHW01 require tweak to the U-Boot environment on update from 22.03 to 23.05. Refer to the Device wiki or the instruction on sysupgrade on how to do this change. Config needs to be reset on sysupgrade.
Known issues
lantiq/xrx200 target shows error messages in DSA switch configuration of the integrated GSWIP switch. (see: https://github.com/openwrt/openwrt/pull/13200)
OpenWrt 23.05.5 was signed with the wrong signing keys. The keys from OpenWrt snapshot were used for OpenWrt 23.05.5, OpenWrt 23.05.4, OpenWrt 23.05.3, OpenWrt 23.05.2, OpenWrt 23.05.0 and the release candidates. A later OpenWrt 23.05 service release will use a different key.
See up to date information here:
https://openwrt.org/releases/23.05/notes-23.05.5#known_issues
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/23.05/notes-23.05.5
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/23.05/notes-23.05.5#known_issues
For a detailed list of all changes since 23.05.4, refer to
https://openwrt.org/releases/23.05/changelog-23.05.5
To download the 23.05.5 images, navigate to:
https://downloads.openwrt.org/releases/23.05.5/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=23.05.5
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:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at https://openwrt.org/contact

37

[Assistant]
Upgraded my two devices.
Linksys E8450 UBI: almost successful. Out of the box, software flow offload works, even for PPPoE:
Problems:
It didn't detect devices connected to the USB hub after the reboot. The hub itself was detected:
root@OpenWrt:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux 5.15.167 xhci-hcd xHCI Host Controller
Bus 001 Device 002: ID 1a86:8095  USB Hub
Bus 001 Device 001: ID 1d6b:0002 Linux 5.15.167 xhci-hcd xHCI Host Controller
After unplugging and replugging it, the devices also showed up:
Bus 001 Device 004: ID 12d1:1506 HUAWEI_MOBILE HUAWEI_MOBILE
Bus 002 Device 001: ID 1d6b:0003 Linux 5.15.167 xhci-hcd xHCI Host Controller
Bus 001 Device 005: ID 152d:2338 JMicron USB to ATA/ATAPI bridge
Bus 001 Device 003: ID 1a86:8095  USB Hub
Bus 001 Device 001: ID 1d6b:0002 Linux 5.15.167 xhci-hcd xHCI Host Controller
EDIT: the USB hub and connected devices survived another router reboot without issues.
The fix that excluded physical devices from the offload did not make it, thus breaking the WiFi roaming. So, I had to apply the full manual fix from https://github.com/openwrt/openwrt/issues/10224#issuecomment-2316382659
The WDS repeater could not reconnect until power-cycling it.
The old Samsung Galaxy A02 phone did not automatically reconnect on 2.4 GHz either.
EDIT: the repeater reconnected fine after another reboot of the router, but the phone didn't.
The repeater itself (Netgear WAX202) was updated without any problems.

1 Reply
1

When can we expect support for eip93 in OpenWrt firmware version 24.x.x?
I have a device based on the MT7621 chipset, and eip93 support is crucial for improving hardware encryption performance. Is there any information on plans to include this driver in a future release?

1 Reply
3

I was just getting near the end of updating all the TOH entries for 23.05.4!

5


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Security Advisory 2022-10-04-1 - wolfSSL buffer overflow during a TLS 1.3 handshake (CVE-2022-39173)

There is a remotely exploitable security issue in wolfSSL library prior to version 5.5.1. In default configuration this applies to OpenWrt releases 21.02 and 22.03, which have LuCI web user interface exposed to local area network clients over HTTPS by uhttpd web server.
Full advisory can be found on a dedicated wiki page.
Package upgrade using command line
You need to update the affected packages you're using with the command below.
opkg update; opkg upgrade libwolfssl libustream-wolfssl
In order to apply the update, you need to either reboot your device or restart affected uhttpd service:
/etc/init.d/uhttpd restart
Then it's recommended to double check, that you're using a fixed version of packages.
opkg list-installed | grep wolfssl
The above command output should contain following fixed versions:
OpenWrt development snapshot
libustream-wolfssl20201210 - 2022-01-16-868fd881-1
libwolfssl5.5.1.e624513f - 5.5.1-stable-8
OpenWrt 22.03 release:
libustream-wolfssl20201210 - 2022-01-16-868fd881-2
libwolfssl5.5.1.ee39414e - 5.5.1-stable-3
OpenWrt 21.02 release:
libustream-wolfssl20201210 - 2022-01-16-868fd881-2
libwolfssl5.5.1.99a5b54a - 5.5.1-stable-2

1 Reply
18

[Assistant]
On my 21.02.3 TP-Link C7v4, after I do opkg update; opkg upgrade libwolfssl libustream-wolfssl , I am still seeing this:
root@Filadelfo:~# opkg list-installed | grep wolfssl
libustream-wolfssl20201210 - 2022-01-16-868fd881-1
libwolfssl5.2.0.99a5b54a - 5.2.0-stable-2
px5g-wolfssl - 3
wpad-basic-wolfssl - 2020-06-08-5a8b3662-40
Are the download sites just not updated yet?
Thanks,
Mike

1 Reply
1

I would like to thank you very much for informing us about this vulnerability. I usually never do updates, I only install new releases.
Have a nice day and greetings to the developers

2

Instructions need to be upgraded to update package px5g-wolfssl to fully remove the dependency on libwolfssl5.4.0.ee39414e.

1 Reply


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Customized image builds via Firmware Selector and ASU/OWUT broken

2025-April-20: Thanks to
@aparcar
and
@efahl
, ASU/OWUT and customized images via the firmware selector should now be working properly. Please report any issues here.
2025-April-19: There is a known issue that affects customized image building via the firmware selector and Attended Sysupgrade (ASU) / OpenWrt Upgrade Tool (OWUT). The system will queue build requests, but does not appear to be executing. As such, the queue has become very long and obviously nobody is able to obtain a customized image.
Please do not create new threads about this issue since it is already known and being discussed here and here.

6

[Assistant]
I believe this issue is completely resolved.
@aparcar
worked on a bunch of stuff to clear the issue, and I've been running tests for a couple of hours without issue. We're putting some stuff into place to eliminate (fingers crossed) the problem in future.
Root cause appears to be server disk filling with build artifacts under high load, like when 24.10.1 was released (we've seen this before and thought it was under control, oops). The first pass has reduced the time-to-live values for builds (that change is live now). We're looking at ways to implement a more effective janitorial service to clear out old junk as soon as it has expired, rather than just doing a once-per-day sweep. There are also some prophylaxis bits to limit the frustration when things do go wrong (hey, it's software, which means there will always be bugs).
(If anyone is curious, just ask, I can point out PRs/code changes and describe what they accomplish.)

1 Reply
7

Thanks for your work
@efahl
and
@aparcar
! I've amended the banner post and I'll keep it live for a day or two just in case any additional issues remain/arise.

1


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 21.02.0 Fourth release candidate

Hi,
The OpenWrt community is proud to announce the fourth release candidate of the upcoming OpenWrt 21.02 stable version series. It incorporates over 5800 commits since branching the previous OpenWrt 19.07 release and has been under development for about one and a half year.
Changes between OpenWrt 21.02.0-rc3 and 21.02.0-rc4
Software updates
Linux kernel: updated to version 5.4.137 (from 5.4.124 in v21.02.0-rc3)
mt76: Update to version 2021-06-06 (from 2021-05-15 in v21.02.0-rc3)
wireguard: Update with recent Linux stable fixes
exfat: Update to version 5.12.3 (from 5.10.1 in v21.02.0-rc3)
Misc changes
failsafe: Fixes failsafe network configuration with swconfig and DSA: FS#3866
odhcpd: fix invalid DHCPv6 ADVERTSIE with small configured leasetime
ugps: parse $GPZDA and $GPGLL sentences, improve interoperability with kplex
netifd: WDS with bridge-vlan fixed
Device support
New devices MikroTik RouterBOARD 912UAG-2HPnD and Joy-IT JT-OR750i
Device fixes for TP-Link CPE, MikroTik RouterBOARDs and AVM FRITZRepeater 1200
Known issues
Some packets from IPv6 streams are getting dropped in software and hardware flow offloading FS#3373
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/21.02/notes-21.02.0-rc4
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.0-rc4#known_issues
For a detailed list of all changes since 21.02.0-rc3, refer to
https://openwrt.org/releases/21.02/changelog-21.02.0-rc4
To download the 21.02.0-rc4 images, navigate to:
https://downloads.openwrt.org/releases/21.02.0-rc4/
To stay informed of new OpenWrt releases and security advisories, there are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at https://openwrt.org/contact
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Have fun!
The OpenWrt Community

40

[Assistant]
Just upgraded from 21.02-snapshot to RC4.
All seems fine.
I was hit by the small lease time for DHCPv6 issue before, which works in RC4 so far.

Hi. I just upgraded my home network to RC4 from RC3. Something seems to be broken with wireless range extending and WDS with RC4. After the upgrade, the wireless range extender can't connect to the base station.
Seems to be the same as the bug report here:
https://bugs.openwrt.org/index.php?do=details&task_id=3961

1 Reply
1

How is it determined which new devices get added to a new release candidate? I would have liked to have the additional devices that were added to the realtek target supported. These are inexpensive readily available devices (Netgear GS308T v1 and Netgear GS310TP v10).

2 Replies
2


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 23.05.0-rc1 first release candidate

Hi,
The OpenWrt community is proud to announce the first release candidate of the upcoming OpenWrt 23.05 stable series.
OpenWrt 23.05.0-rc1 incorporates over 3900 commits since branching the previous OpenWrt 22.03 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:
https://firmware-selector.openwrt.org/?version=23.05.0-rc1
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/23.05.0-rc1/targets/
Highlights in OpenWrt 23.05.0:
Many new devices added
OpenWrt 23.05 supports over 1750 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 22.03.
The ipq807x target for the Qualcomm IPQ807x Wifi 6 SoCs was added
Highlights of device support
Switched ipq40xx target to DSA
VDSL support on AVM FRITZ!Box 7530
Support for devices with 2.5G PHYs
Netgear WAX206 (MT7622)
Asus (TUF Gaming) AX4200 (MT7986A)
Netgear WAX218 (IPQ8074)
Xiaomi AX9000 (IPQ8074)
Dynalink DL-WRX36 (IPQ8074)
Improved DSL statistics on ubus and in LuCI
Switch from wolfssl to mbedtls as default
OpenWrt switched the default cryptographic library from wolfssl to mbedtls. This library is used for HTTPS/TLS in the Webserver providing LuCI and for the cryptographic operations in hostapd. mbedtls provides security updates in their LTS branch without changing the application binary interface (ABI) of the library. wolfssl provides a stable ABI only for a very limited subset of functions. mbedtls allows us to update only mbedtls without the need to recompile and upgrade all users of mbedtls.
Core components update
Core components have the following versions in 23.05.0-rc1:
Updated toolchain:
musl libc 1.2.4
glibc 2.37
gcc 12.3.0
binutils 2.40
Updated Linux kernel
5.15.114 for all targets
Network:
hostapd master snapshot from March 2023
dnsmasq 2.89
dropbear 2022.82
cfg80211/mac80211 from kernel 6.1.24
System userland:
busybox 1.36.1
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/23.05/notes-23.05.0-rc1
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/23.05/notes-23.05.0-rc1#known_issues
For a detailed list of all changes since 22.03.0, refer to
https://openwrt.org/releases/23.05/changelog-23.05.0-rc1
To download the 23.05.0-rc1 images, navigate to:
https://downloads.openwrt.org/releases/23.05.0-rc1/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=23.05.0-rc1
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:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact

2 Replies
36

[Assistant]
I would love to see the SDK git initialization be fixed before release
github.com/openwrt/openwrt
sdk: fix git initialization
committed
Apr 9, 2023
mpratt14
+16 -6
The extra Makefile prepare.mk
is not being installed in the right place.
We have…

1

Outstanding news for this long time awaited version. Congratulations to the devs team and everyone involved.
Do you mind adding in the release note that the Linksys EA8300, MR8300, EA6350v3 devices can't install/upgrade to 23.05.0-rc1 unless a boot variable change ? Without, this will soft-brick the device. Please link to the installation note.
OpenWrt Wiki – 31 Aug 21
Linksys MR8300
Linksys MR8300 [EA8300] The Linksys MR8300 is very close to the EA8300, so basic infos from one should also apply to the other. The Linksys MR8300 is a MU-MIMO Tri-Band WiFi router, which has one 2.4GHz and two 5GHz WiFi Interfaces, making it an...

10

Also of interest to ARM users, not sure if it's in the RC1...
github.com/openwrt/openwrt
[23.05] armvirt: add EFI support + rename to armsr
openwrt:openwrt-23.05 ← mcbridematt:openwrt-2305-add-efi
opened
Jun 5, 2023
mcbridematt
+1831 -451
This is the 23.05 / 5.15 kernel version of https://github.com/openwrt/openwrt/pu…
github.com/openwrt/openwrt
armvirt: rename to 'armsr'
openwrt:main ← mcbridematt:armvirt-rename-armsr
opened
Jun 7, 2023
mcbridematt
+61 -443
As discussed in https://github.com/openwrt/openwrt/pull/12817#issuecomment-15783…


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 21.02.5 fifth service release

Hi,
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 21.02 stable version series. It fixes security issues.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=21.02.5
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/21.02.5/targets/
The OpenWrt 21.02 stable series is in security maintenance only mode. It is projected to go end of life on 6. April 2023 following the OpenWrt Security support guidelines. We encourage all users of the OpenWrt 21.02 stable series to upgrade to OpenWrt 22.03.
https://openwrt.org/docs/guide-developer/security#support_status
Main changes between OpenWrt 21.02.4 and OpenWrt 21.02.5:
Security fixes
mac80211/cfg80211: Security fixes for BSSID parsing (CVE-2022-41674, CVE-2022-42719, CVE-2022-42720, CVE-2022-42721 and CVE-2022-42722)
See Security Advisory 2022-10-17-1
Device support
None
Various fixes and improvements
None
Core components
None
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/21.02/notes-21.02.5
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.5#known_issues
For a detailed list of all changes since 21.02.4, refer to
https://openwrt.org/releases/21.02/changelog-21.02.5
To download the 21.02.5 images, navigate to:
https://downloads.openwrt.org/releases/21.02.5/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=21.02.5
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:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at https://openwrt.org/contact

8

[Assistant]
Thanks to all the OpenWrt developers.
Six hours up
and
All appears to be fine on a Archer C2600 v1.1 with BanIP, Adblock and irqbalance.

There's a regression on TP-Link TL-WDR4900 v1 (mpc85xx/p1010). Wifi is down after upgrade. It looks like from the 21.02.3 -> 21.02.4 upgrade, but still in 21.02.5 - see https://github.com/openwrt/openwrt/issues/11002 for details. Workaround is to manually fixup /etc/config/wireless and then remove or edit /etc/hotplug.d/ieee80211/05-wifi-migrate

I keep getting this alot after switching to 21.02.5.
when installing packages.
pkg_hash_check_unresolved: cannot find dependency kernel (= 5.4.215-1-eef61aad9d9205d0f312846abba7ba7f)


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 19.07.5 service release

Hi,
The OpenWrt community is proud to announce the newest service release in the 19.07 stable series: OpenWrt 19.07.5. It focuses on fixing several regression as well as security issues.
Selected highlights of this service release are:
Security fixes
Security Advisory 2020-12-09-2 - libuci import heap use after free (CVE-2020-28951)
Security Advisory 2020-12-09-1 - Linux kernel - ICMP rate limiting can be used to facilitate DNS poisoning attack (CVE-2020-25705)
musl: fix possible destination buffer overflow in some applications (CVE-2020-28928)
Various security fixes in packages
Major bug fixes
Fix regression in 19.07.4 causing transmit timeout and packet loss on mt7620 devices
Fix regression in 19.07.4 where VLAN tagging no longer works on ipq40xx devices
Fix long-standing instability issue on Ethernet link on several ath79 devices
Device support
Various fixes for My Net Range Extender, PowerCloud Systems CAP324, D-Link DIR-645, Quad-E4G
Support newer version of Turris Omnia
Fix ath9k firmware extraction for UniFi AP
Fix MAC address assignment on UniFi AC family (UniFi AC Mesh, UniFi AC LR, UniFi Lite)
Allow booting espressobin with a mainline firmware
Full release notes and upgrade instructions are available, as well as a detailed list of all changes since 19.07.4. Make sure to read the regressions and known issues before upgrading.
For latest information about the 19.07 series, refer to the wiki page.
To download a OpenWrt 19.07.5 firmware image for your device, head to the Table of Hardware or navigate directly in the list of firmware images.
OpenWrt Firmware Selector
We also have the newer option of the OpenWrt Firmware Selector. Please provide feedback about it in the dedicated thread.
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Have fun!
The OpenWrt Community

42

[Assistant]
I upgraded by Linksys WRT3200ACM to the new release and everything seems fine. Thanks for pushing out these security fixes!

1 Reply
2

Why was no announcement sent to the announcements mailing list?
lists.openwrt.org
The openwrt-announce Archives

1 Reply
4

upgraded smoothly to archer C7V2 and wdr4900v2. work fine.
Just still no WAN & LAN leds export in /sys/class/leds.
Congratulation to developers.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: A note about using new stable releases before they are announced

There is always an excitement and enthusiasm as new stable releases start showing up on the downloads page -- and that is great! As of this moment, 21.02.3 and 19.07.10 are currently building, but they are not complete nor are they announced (current versions are still 21.02.2 and 19.07.9). Over time, the 'current' and upcoming versions will be different, but the same principles apply.
A few things to know before you try to install new versions prior to the official announcement:
The build system may still be running, and it is a pretty big job. It typically takes several days for everything to complete. The official announcement will come after everything is done.
Because of the fact that the builds take time, you may find that some targets/platforms are ready and others are not. This will almost always resolve with time as the build progresses.
The same is true with user-installable packages -- it may appear that packages are missing, but really they just haven't been built yet.
There is a relatively small chance that a problem will arise during the build process that may cause the build to fail. If this happens, the dev team may need to fix the issue and begin the build process again. Although it is quite unlikely, it is plausible that this could even include a major bug,
For all of these reasons, it is not recommended to install a new version before it is officially announced. And, if you choose to install, just remember that things are potentially still in flux, including packages you might rely on.

1 Reply
54

[Assistant]
I would add that if you do decide to upgrade before the release announcement, make sure to backup your configuration files, and know how to recover your device (TFTP, serial) BEFORE doing the actual upgrade...in case something goes sideways.

I'd also add that quite a few have flash warnings that stop sysupgrade.
I haven't found any documentation detailing this screen yet or what to do with devices where it appears (e.g. Meraki MX60).

1

With experienced Linux users, the first thing to do when seeing such warnings is to check the manpage of sysupgrade. And it is easy to spot the --force option to force an upgrade and ignore the warnings.
Windows users being Windows users; if you want to help them, the best way is to put a GUI option on LuCI.

2 Replies


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 21.02.0 third release candidate

Hi,
The OpenWrt community is proud to announce the third release candidate of the upcoming OpenWrt 21.02 stable version series. It incorporates over 5800 commits since branching the previous OpenWrt 19.07 release and has been under development for about one and a half year.
Changes between OpenWrt 21.02.0-rc2 and 21.02.0-rc3
LuCI
LuCI network migration tool now migrates custom bridge MAC addresses.
Software updates
Linux kernel updated to version 5.4.124 (from 5.4.119 in v21.02.0-rc2)
mac80211 updated to version 5.10.42-1 (from 5.10.34-1 in v21.02.0-rc2)
wireless-regdb updated to version 2021.04.21 (from 2020.11.20 in v21.02.0-rc2)
Misc changes
opkg: Shows better error message when some dependencies are missing
sdk, imagebuilder: json-c, libnl-tiny, libubox, ubus, uci and lua are marked nonshared and will be taken from release build and not package build.
Device support
New devices: SERCOMM NA502, Linksys EA8100 v1, Amped Wireless ALLY, Linksys E5600, JCG Q20, cudy WR2100, TP-Link Archer C6U v1 (EU), TP-Link Archer A6 v3, ZyXEL NR7101, ZTE MF283+
Device fixes for: Xiaomi Router 3 Pro, HILINK HLK-7628N, WD My Net Wi-Fi Range Extender, ALLNET ALL-WAP02860AC, Senao APs, TP-Link AD7200
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/21.02/notes-21.02.0-rc3
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.0-rc3#known_issues
For a detailed list of all changes since 21.02.0-rc2, refer to
https://openwrt.org/releases/21.02/changelog-21.02.0-rc3
To download the 21.02.0-rc2 images, navigate to:
https://downloads.openwrt.org/releases/21.02.0-rc3/
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Have fun!
The OpenWrt Community

1 Reply
32

[Assistant]
Mesh Routing
olsrd: procd and version update, further fix compiling with glibc
babeld: update to 1.10

1

Hi,
known issue : since any release > 20.x => DHCPv6 strange behaviour:
if leasetime set < 12h then no more DHCPv6 lease given to any client, no more IPV6-PD to any downstream router
if downstream router asks for a smaller prefix than the one given to the lan iface from the upstream routeur then (for eg. downstream asks for a /60 when the upstream has a delegated /60 or bigger /61 /62 ...):
the downstream router will get, sometimes but not always, a prefix OUTSIDE the delegated scope from the upstream router
the downstream router will also get a prefix even from a class not allowed to the upstream LAN interface (outside the ip6assign parameters)
otherwise for me everything else is perfect, thank you for this great job!
regards

3

Hopefully someone can add support for 64bit odhcpd static hostid. https://github.com/openwrt/odhcpd/issues/27

1


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 24.10.0-rc7 - Seventh Release Candidate

Hi,
The OpenWrt community is proud to announce the seventh release candidate of the upcoming OpenWrt 24.10 stable series.
OpenWrt 24.10.0-rc7 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:
https://firmware-selector.openwrt.org?version=24.10.0-rc7
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/24.10.0-rc7/targets/
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
If there is already an existing ticket feel free to comment that the problem also occurs with OpenWrt 24.10.0-rc7.
Changes between OpenWrt 24.10.0-rc6 and 24.10.0-rc7
Target changes:
airoha: multiple fixes
apm821xx: NETGEAR WNDR4700: fix compat version
ath79: make kmod-usb-chipidea select kmod-phy-ath79-usb
ipq40xx: AVM FRITZ!Box 7530: fix ADSL/ATM operation
mediatek: Cudy M3000 / Cudy TR3000: fixes 2.5G PHY interrupt support
mediatek: Cudy TR3000: update status led
mediatek: Netgear wax206: fix wifi leds
mediatek: Xiaomi AX3000T: add Airoha AN8855 gigabit switch driver
octeon: ubnt-usg: add board name to supported devices
qualcommax: Spectrum SAX1V1K: add missing WAN LED support
ramips: USW-Flex: restore full switch performance
realtek: HPE 1920-8G PoE: fix old compatible
stm32: enable CONFIG_SMSC_PHY
Generic changes:
dnsmasq: add fix related to DNSSEC verification from upstream
generic: fix probe issues with RealTek RTL8221B PHYs
unetd: fix interface teardown
wolfssl: update to version 5.7.6
For a detailed list of changes since OpenWrt 24.10.0-rc7 see the 24.10.0-rc7 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.
Added support for OpenWrt One
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
Added support for Airoha AN8855 DSA Switch (Xiaomi AX3000T ship both Mediatek and Airoha Switch in the same revision)
Core components update
Core components have the following versions in 24.10.0-rc7:
Updated toolchain:
musl libc 1.2.5
glibc 2.38
gcc 13.3.0
binutils 2.42
Updated Linux kernel
6.6.73 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.
Known issues
LEDs handling for Airoha AN8855 is currently not supported. Xiaomi AX3000T with Airoha Switch mounted will have Switch LEDs powered OFF. (problem will be addressed in later OpenWrt SNAPSHOT and later Openwrt 24.10 minor release)
5GHz Wifi on TP-Link Archer C60 v1, TP-Link Archer C6 v2 and probably more devices with ath10k Wifi chip does not work, see https://github.com/openwrt/openwrt/issues/14541
Ethernet link unstable on some mt7530 switches. Deactivate EEE (Energy-Efficient Ethernet) as a workaround, see: https://github.com/openwrt/openwrt/issues/17351
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.0-rc7
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.0-rc7#known_issues
For a detailed list of all changes since 24.10.0-rc5, refer to
https://openwrt.org/releases/24.10/changelog-24.10.0-rc7
To download the 24.10.0-rc7 images, navigate to:
https://downloads.openwrt.org/releases/24.10.0-rc7/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=24.10.0-rc7
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:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact

16

[Assistant]
@aparcar
We have two missing targets this time, looks like the docker containers for image builders are there, but the targets are not in the 24.10 branch data.
From two owut tests:
Unsupported target: bmips/bcm6358
Unsupported target: ramips/mt7621

1 Reply
2

RC7 up and running on my GL-MT6000. Running great. Thanks to the devs.

1

Updated without any issues:
GL.iNet GL-MT6000 (Flint 2) (mediatek/filogic)
GL.iNet GL-MT3000 (Beryl AX) (mediatek/filogic)
Dynalink DL-WRX36 (qualcommax/ipq807x)

3


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User] Q: OpenWrt Summit and BattleMesh v17 Official Announcement – 13–15 June 2025, Sundhausen, Thuringia, Germany

[Assistant]
Hi,
We are excited to announce the 17th edition of the Wireless Battle of the Mesh and the co-hosted OpenWrt Summit! This event aims to further the discussion on the right to connectivity, community-owned infrastructure, and related free open source projects.
Event Details:
Date: 10–16 June 2025 (7 days) (BattleMesh)
Date: 13–15 June 2025 (3 days) (OpenWrt Summit)
Venue: Sundhausen, Thuringia, Germany (51°09'25.1"N 10°43'00.7"E)
Cost: Free and open to everyone
The OpenWrt Summit is co-hosted at the BattleMesh v17. If you want to give a workshop or talk please propose your session in the BattleMesh CfP.
Registration:
Please add yourself to the participants list here: https://www.battlemesh.org/BattleMeshV17/Participants
If you’d prefer not to have your name displayed publicly, kindly email the organization team (battlemeshv17-orga@freifunk.net) with the same details.
Accommodation Options:
Camping: Self-organized, free of charge
Apartments: Contact the organization team (very limited, charges apply)
More details: https://battlemesh.org/BattleMeshV17/Accomodation
Visa & Travel Support:
The University of Nordhausen offers visa invitation letters. Please reach out to the organization team with your details if needed.
Travel support may be available on a case-by-case basis — simply email the team with your background.
Additional Information:
Directions: https://battlemesh.org/BattleMeshV17/Directions
Workshop/Session Ideas (CfP): https://battlemesh.org/BattleMeshV17/CfP
More about the event: https://www.battlemesh.org/BattleMeshV17
Please help us spread the word by sharing this announcement.
Best regards

7


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 23.05.0-rc3 - Third Release Candidate

Hi,
The OpenWrt community is proud to announce the third release candidate of the upcoming OpenWrt 23.05 stable series.
OpenWrt 23.05.0-rc3 incorporates over 4200 commits since branching the previous OpenWrt 22.03 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:
https://firmware-selector.openwrt.org/?version=23.05.0-rc3
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/23.05.0-rc3/targets/
Changes between OpenWrt 23.05.0-rc2 and 23.05.0-rc3
Changes in this release candidate since the previous 23.05.0-rc2 release candidate are:
New devices
ath79: MikroTik RB951G-2HnD
ipq40xx: Teltonika RUTX50
ipq40xx: ZTE MF287+ aka DreiNeo
layerscape: Traverse Ten64 NAND variant
mediatek: Acer Predator W6
mediatek: H3C Magic NX30 Pro
mediatek: Mercusys MR90X v1
mediatek: Netgear EX6250v2 series (no wifi support)
mediatek: Xiaomi WR30U
mediatek: ZyXEL NWA50AX Pro
ramips: Sercomm S1500 devices
ramips: TP-Link EAP613 v1
realtek: HPE 1920-8g-poe+
Updated components:
hostapd: update to 2023-06-22
mt76: update to 2023-07-26
ath11k-firmware: update to stable WLAN.HK.2.9.0.1-01837
openssl: update to 3.0.10
mbedtls: Update to 2.28.4
wolfssl: update to 5.6.3
intel-microcode: update to 20230808
linux-firmware: update to 20230804
kernel: bump 5.15 to 5.15.127
ramips: mt7621: disable the cpufreq driver (performance increase)
ramips: mt7621: disable highmem support and remove highmem offset patch (performance increase)
uqmi: support split-APN IPv4 and IPv6 dual-stack
iwinfo/rpcd: update byte counter to 64bit
x86: Activate CONFIG_PCIEASPM
x86: Add virtualization time sync support
armsr: activate many new configuration options
kernel: modules: add xdp-sockets-diag support
ipq40xx: meraki: define DTB load address
ath79: move ubnt-xm 64M RAM boards back to generic
lua: fix integer overflow in LNUM patch
Many other changes in all parts of OpenWrt, see Chnagelog for details.
Highlights in OpenWrt 23.05.0:
Many new devices added
OpenWrt 23.05 supports over 1794 devices. Support for over 200 new devices was added in addition to the device support by OpenWrt 22.03.
The ipq807x target for the Qualcomm IPQ807x Wifi 6 SoCs was added
The mediatek/filogic subtarget for the Mediatek Filogic 830 and 630 SoCs was added
The sifiveu target for the HiFive RISC-V Unleashed and Unmatched boards
Highlights of device support
Switched ipq40xx target to DSA
VDSL support on AVM FRITZ!Box 7530
Support for devices with 2.5G PHYs
Acer Predator W6 (MT7986A)
Mercusys MR90X v1 (MT7986BLA)
Netgear WAX206 (MT7622)
Netgear WAX220 (MT7986)
ZyXEL NWA50AX Pro (MT7981)
Asus (TUF Gaming) AX4200 (MT7986A)
Netgear WAX218 (IPQ8074)
Xiaomi AX9000 (IPQ8074)
Dynalink DL-WRX36 (IPQ8074)
2 Gbps WAN/LAN NAT Routing on ramips MT7621 devices
Improved DSL statistics on ubus and in LuCI
Switch from wolfssl to mbedtls as default
OpenWrt switched the default cryptographic library from wolfssl to mbedtls. This library is used for HTTPS/TLS in the Webserver providing LuCI and for the cryptographic operations in hostapd. mbedtls provides security updates in their LTS branch without changing the application binary interface (ABI) of the library. wolfssl provides a stable ABI only for a very limited subset of functions. mbedtls allows us to update only mbedtls without the need to recompile and upgrade all users of mbedtls.
Core components update
Core components have the following versions in 23.05.0-rc3:
Updated toolchain:
musl libc 1.2.4
glibc 2.37
gcc 12.3.0
binutils 2.40
Updated Linux kernel
5.15.127 for all targets
Network:
hostapd master snapshot from June 2023
dnsmasq 2.89
dropbear 2022.82
cfg80211/mac80211 from kernel 6.1.24
System userland:
busybox 1.36.1
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/23.05/notes-23.05.0-rc3
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/23.05/notes-23.05.0-rc3#known_issues
For a detailed list of all changes since 23.05.0-rc2, refer to
https://openwrt.org/releases/23.05/changelog-23.05.0-rc3
To download the 23.05.0-rc3 images, navigate to:
https://downloads.openwrt.org/releases/23.05.0-rc3/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=23.05.0-rc3
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
Have fun!
The OpenWrt Community

35

[Assistant]
Can't install wget-ssl on WRT1900ACS v1:
opkg_download: Failed to download https://downloads.openwrt.org/releases/23.05.0-rc3/packages/arm_cortex-a9_vfpv3-d16/packages/wget-ssl_1.21.3-2_arm_cortex-a9_vfpv3-d16.ipk, wget returned 8.
wget package files are missing. Without wget DynamicDNS doesn't function.

2 Replies
1

works well on minimalist low energy ea3500 security router. will test later on dozen other routers and switches comprising home/office network w/ ruckus master switch & ap's.

After a 55 day uptime with rc2 just flashed rc3 on my WRT32X. Installed a lot of typical packages: SQM, Samba, Simple-Adblock, Advanced-Reboot, etc. All working great.
The Overview screen with new Port Status looks nice too.
Interestingly an SQM Cake bufferbloat test showed load fairly balanced across CPU0 and CPU1 than I remember looking at htop. It's 30-50% load on both cores during max download. This is a good thing, I recall most load being on CPU0 with mvebu, and CPU1 having far less. Anyway I'll keep an eye on it (I know the new sqm-scripts didn't make it in but that wouldn't affect this).
[https://www.waveform.com/tools/bufferbloat?test-id=7f54025b-a6aa-4191-aa19-18d0ef64b58a]
Anyway, thanks devs for the great release!

5


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 23.05.0 - First stable release

Hi,
The OpenWrt community is proud to announce the first stable release of the OpenWrt 23.05 stable series.
OpenWrt 23.05.0 incorporates over 4300 commits since branching the previous OpenWrt 22.03 release and has been under development for over one year.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=23.05.0
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/23.05.0/targets/
Highlights in OpenWrt 23.05.0:
Many new devices added
OpenWrt 23.05 supports over 1790 devices. Support for over 200 new devices was added in addition to the device support by OpenWrt 22.03.
The ipq807x target for the Qualcomm IPQ807x Wifi 6 SoCs was added
The mediatek/filogic subtarget for the Mediatek Filogic 830 and 630 SoCs was added
The sifiveu target for the HiFive RISC-V Unleashed and Unmatched boards
Highlights of device support
Switched ipq40xx target to DSA
VDSL support on AVM FRITZ!Box 7530
Support for devices with 2.5G PHYs
Acer Predator W6 (MT7986A)
Mercusys MR90X v1 (MT7986BLA)
Netgear WAX206 (MT7622)
Netgear WAX220 (MT7986)
ZyXEL NWA50AX Pro (MT7981)
Asus (TUF Gaming) AX4200 (MT7986A)
Netgear WAX218 (IPQ8074)
Xiaomi AX9000 (IPQ8074)
Dynalink DL-WRX36 (IPQ8074)
GL.iNet GL-MT6000 (MT7986A)
ZyXEL EX5700 (MT7986)
Support for Wifi 6E (6GHz)
Acer Predator W6 (MT7986A)
ZyXEL EX5700 (MT7986)
2 Gbps WAN/LAN NAT Routing on ramips MT7621 devices (See OpenWrt forum)
Improved DSL statistics on ubus and in LuCI
Added Arm SystemReady (EFI) compliant target replacing the armvirt target
Switch from wolfssl to mbedtls as default
OpenWrt has transitioned its default cryptographic library from wolfssl to mbedtls. This shift brings several changes and implications:
Size Efficiency: mbedtls is considerably smaller, making it an optimal choice for systems where storage space is paramount.
LTS and ABI Stability: mbedtls consistently provides updates via its Long Term Support (LTS) branch, ensuring both security and a stable application binary interface (ABI). In contrast, wolfssl does not offer an LTS release, and its stable ABI is limited to a specific set of functions.
TLS 1.3 Support: Users should be aware that mbedtls 2.28 no longer supports TLS 1.3.
While mbedtls is now the default, users who have specific needs or preferences can still manually switch back to wolfssl or choose openssl.
Rust Package Support
This release introduces the ability to include rust-written programs into the OpenWrt package infrastructure. Examples are: bottom, maturin, aardvark-dns and ripgrep.
Core components update
Core components have the following versions in 23.05.0:
Updated toolchain:
musl libc 1.2.4
glibc 2.37
gcc 12.3.0
binutils 2.40
Updated Linux kernel
5.15.134 for all targets
Network:
hostapd master snapshot from September 2023
dnsmasq 2.89
dropbear 2022.82
cfg80211/mac80211 from kernel 6.1.24
System userland:
busybox 1.36.1
Upgrading to 23.05.0
Sysupgrade can be used to upgrade a device from 22.03 to 23.05, and configuration will be preserved in most cases.
Sysupgrade from 21.02 to 23.05 is not officially supported.
ipq40xx EA6350v3, EA8300 and MR8300 require tweak to the U-Boot environment on update from 22.03 to 23.05. Refer to the Device wiki or the instruction on sysupgrade on how to do this change. Config needs to be reset on sysupgrade.
Known issues
lantiq/xrx200 target is not build because the DSA driver for the integrated GSWIP switch shows some error messages. (see: https://github.com/openwrt/openwrt/pull/13200)
bcm53xx: Netgear R8000 and Linksys EA9200 Ethernet is broken (see: https://github.com/openwrt/openwrt/issues/13548)
default gateway setting is not applied when using the wifi device in station mode. (see: https://github.com/openwrt/openwrt/issues/13598)
The prebuilt images for Zyxel NR7101 are currently broken and will brick your device. PLEASE DO NOT INSTALL. (bug already fixed but require SNAPSHOT or self-compile)
realtek: there is currently a problem with MAC address getting wiped on installing 23.05.0. A fix is in progress has been merged and the correct MAC address will be restored on 23.05.1 (see: https://github.com/openwrt/openwrt/pull/13622)
OpenWrt 23.05.0 was signed with the wrong signing keys. The keys from OpenWrt snapshot were used for OpenWrt 23.05.0 including the release candidates. A later OpenWrt 23.05 service release will use a different key.
In Mesh only configuration for WiFi 2.4GHz, force 40MHz option is ignored and doesn't work. Problem has been bisected, fixed in main and backported in 23.05. Normal function will be restored on 23.05.1 (see: https://github.com/openwrt/openwrt/pull/13909)
See up to date information here:
https://openwrt.org/releases/23.05/notes-23.05.0#known_issues
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/23.05/notes-23.05.0
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/23.05/notes-23.05.0#known_issues
For a detailed list of all changes since 22.03.0, refer to
https://openwrt.org/releases/23.05/changelog-23.05.0
To download the 23.05.0 images, navigate to:
https://downloads.openwrt.org/releases/23.05.0/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=23.05.0
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:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at https://openwrt.org/contact

12 Replies
47

[Assistant]
Thank you for the new release, I am excited about the new features and hardware support
An issue that might need to be added to the known issues list: https://github.com/openwrt/openwrt/issues/13598 - under some circumstances, the system might fail to set a default route after reboot. I'm not entirely sure what triggers the bug yet, but as far as I can tell it happens when an interface is set up as a wifi client (no wired devices attached), with option proto 'static' and an option gateway configured. The issue is that the option gateway does not actually take effect after a reboot.

2

Binary builds are still going, it seems? At the time of this posting, ipq40xx generic targets aren't on the downloads site.

1 Reply
2

I have upgraded 15min ago Netgear "Nighthawk X4S R7800". Many thanks to all developers and other contributors.
A first test with 8K streaming was successful, the upgrade went very well as always.

3 Replies
7


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 21.02.0 first release candidate

Hi,
The OpenWrt community is proud to announce the first release candidate of the upcoming OpenWrt 21.02 stable version series. It incorporates over 5800 commits since branching the previous OpenWrt 19.07 release and has been under development for about one and a half year.
WPA3 support included by default
WPA3 was already supported in 19.07 but it was not provided by the default set of packages in OpenWrt images.
With 21.02, all packages necessary to provide WPA3 are installed by default in OpenWrt images.
TLS and HTTPS support included by default
TLS support is now provided by default in OpenWrt images including the trusted CA certificates from Mozilla. It means that wget and opkg now support fetching resources over HTTPS out-of-the-box. The opkg download server is accessed through HTTPS by default. OpenWrt switched from mbed TLS to wolfSSL as the default SSL library, mbed TLS and OpenSSL are still available and can be installed manually.
Initial DSA support
DSA stands for Distributed Switch Architecture and is the Linux standard to deal with configurable Ethernet switches.
OpenWrt 21.02 comes with initial support for DSA, which replaces the swconfig system that OpenWrt was using up until now. Not all targets have been ported: some devices still use swconfig while some devices already switched to DSA.
This is a significant change to how switch ports and VLANs are managed. As such, sysupgrade will not be able to convert existing swconfig configuration to DSA configuration (see “Upgrading” below).
The following targets are using a switch managed with DSA in OpenWrt 21.02:
ath79 (only TP-Link TL-WR941ND)
bcm4908
gemini
kirkwood
mediatek (most boards)
mvebu
octeon
ramips/mt7621
realtek
Increased minimum hardware requirements: 8 MB flash, 64 MB RAM
Due to new features being introduced and the general size increase of the Linux kernel, devices now need at least 8 MB of flash and 64 MB of RAM to run a default build of OpenWrt.
It is still possible to build custom OpenWrt images (e.g. using the ImageBuilder) that may fit devices with 4 MB of flash or 32 MB of RAM. However, the level of functionality will be reduced and there is no guarantee to stability. See OpenWrt on 4/32 devices for more details and guidance.
New hardware targets
A new realtek target has been added, which is often found in managed switches. As a result, it is now possible to run OpenWrt on devices with a significant number of Ethernet ports. See supported devices for realtek.
In addition, new bcm4908 and rockchip targets have been added.
Support for many new boards was added to the existing targets.
Dropped hardware targets
The ar71xx was deprecated in OpenWrt 19.07 and was gradually replaced by ath79, see ar71xx-ath79 migration. With OpenWrt 21.02, the ar71xx has been removed and users must use ath79 instead. If you are still running with the ar71xx target, it is recommended to reinstall OpenWrt 21.02 from scratch. Users already on the ath79 target can use sysupgrade to upgrade to OpenWrt 21.02.
Other targets were also removed: cns3xxx, rb532 and samsung.
ASLR activated
Network exposed user space applications are linked as position-independent executable (PIE) to allow full Address Space Layout Randomization (ASLR) support. This makes it harder for attackers to exploit OpenWrt. See Hardening build options for more details.
Kernel with container support
Multiple Linux kernel compile options, needed for Linux Containers (LXC) and procd-ujail are activated by default for most targets. This allows to use LXC and ujail with the normal release builds.
SELinux support
It is possible to compile OpenWrt with SELinux support. This is currently not activated by default.
Core components update
Core components have the following versions in 21.02.0-rc1:
Updated toolchain:
musl libc 1.1.24
glibc 2.33
gcc 8.4.0
binutils 2.35.1
Updated Linux kernel
5.4.111 for all targets
Network:
hostapd 2020-06-08, dnsmasq 2.84, dropbear 2020.81
cfg80211/mac80211 from kernel 5.10.16
wireguard backport from upstream Linux kernel
System userland:
busybox 1.33.0
In addition to the listed applications, many others were also updated.
Upgrading to 21.02.0-rc1
Sysupgrade can be used to upgrade a device from 19.07 to 21.02, and configuration will be preserved in most cases.
Sysupgrade from 18.06 to 21.02 is not supported.
There is no migration path for targets that switched from swconfig to DSA. In that case, sysupgrade will refuse to proceed with an appropriate error message:
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
The default root file system partition size changed for targets/devices relying on booting from mass storage (HDD, USB flash, SD card, etc.), so MBR will change and any additional partition will be deleted when sysupgrading.
Known issues
DSA support is new and might not be complete or fully working
The LuCI web interface has no support for DSA yet
LuCI writes unnecessary IPv6 RA options to /etc/config/dhcp if the
user edits interface's DHCP settings. This could prevent client IPv6
connectivity.
Update luci-mod-network to git-21.107.58557 or later to fix this
problem
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/21.02/notes-21.02.0-rc1
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.0-rc1#known_issues
For a very detailed list of all changes since 19.07, refer to
https://openwrt.org/releases/21.02/changelog-21.02.0-rc1
To download the v21.02.0-rc1 images, navigate to:
https://downloads.openwrt.org/releases/21.02.0-rc1/
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements: https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum: https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Have fun!
The OpenWrt Community

3 Replies
43

[Assistant]
hauke:
Known issues
...
LuCI writes unnecessary IPv6 RA options to /etc/config/dhcp if the
user edits interface's DHCP settings. This could prevent client IPv6
connectivity.
Update luci-mod-network to git-21.107.58557 or later to fix this
problem
Slight correction to this advice. The fixed luci-mod-network is git-21.110.65613 or newer.
https://github.com/openwrt/luci/commit/af7a61d3a6c7bd6ceef03d4a2ad70b0366ad9d38
(My bad, I originally looked up the fixed version wrongly for Hauke)

1 Reply

I tried the RC on my CPE 210 v1 and it bootlooped afterwards. Also if I flashed it again through TFTP and regardless if I use the factory or sysupgrade image. After recovering using a 19.07.7 image it works fine again. A 21.02 snapshot build from a month or so ago worked fine on the same device.
I did not capture serial logs because that device is still sealed and on my roof.
Anyone else having issues?

3 Replies

What's about multiple identical mt76x8 devices like tl-wr840n v4,v5 & tl-wr850n v1,v2? There is no need to separate dts files for those devices. One build can run into other devices without any problems. So, don't make dts list so long, it is necessary to merge these devices in one dts file.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 19.07.4 service release

Hi,
The OpenWrt community is proud to announce the newest service release in the 19.07 stable series: OpenWrt 19.07.4. It focuses on stability and device support.
Selected highlights of this service release are:
fix regression in libubox causing some services to fail to start
fix regression in the LuCI web interface: the menu was not showing newly installed opkg packages
fix a bug in musl that could crash applications in rare circumstances. Fastd, a VPN daemon, seems to be particularly affected by this bug
fix support for several devices that failed to boot
many other fixes and improvements to device support
update core components (linux kernel, mac80211, ath10k-ct-firmware)
Full release notes and upgrade instructions are available, as well as a detailed list of all changes since 19.07.3. Make sure to read the regressions and known issues before upgrading.
For latest information about the 19.07 series, refer to the wiki page.
To download a OpenWrt 19.07.4 firmware image for your device, head to the Table of Hardware or navigate directly in the list of firmware images.
Finally, we have a new mailing list for important announcements and security advisories. Announcements should also be posted to this forum section.
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Have fun!
The OpenWrt Community

40

[Assistant]
You can use this topic to share your upgrading experience: did it work, did you run into issues?
In case of issues, please check for existing topics in https://forum.openwrt.org/c/general/6 (or create a new one) and then post here to provide a summary and a link. Let's keep this topic as readable as possible.

2 Replies

Just upgraded to my Archer C7 v2 but I keep having to switch to the regular qca988x firmware to get better throughput. No issues other than that.

1 Reply
2

Idid clean install on Asus rt-n56u vB. All is fine, much awaited release.
I have wpa3 working in mixed wpa2-psx mode


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 24.10.0-rc5 - Fifth release candidate

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:
https://firmware-selector.openwrt.org?version=24.10.0-rc5
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/24.10.0-rc5/targets/
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.
Added support for OpenWrt One
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:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact

18

[Assistant]
Still seeing this on x86

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 Reply
1

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.

2

JustAnotherEndUser:
Appears to be minor build issue not affecting my config.
Right, that's just informational and hence the green text telling you that you are not at risk.
JustAnotherEndUser:
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 )
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


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt 21.02.0 - First Stable Release

Hi,
The OpenWrt community is proud to announce the first stable release of the OpenWrt 21.02 stable version series. It incorporates over 5800 commits since branching the previous OpenWrt 19.07 release and has been under development for about one and a half year.
Highlights in OpenWrt 21.02.0
WPA3 support included by default
WPA3 was already supported in 19.07 but it was not provided by the default set of packages in OpenWrt images.
With 21.02, all packages necessary to provide WPA3 are installed by default in OpenWrt images. WPA3 is supported by most Wifi drivers in OpenWrt.
TLS and HTTPS support included by default
TLS support is now provided by default in OpenWrt images including the trusted CA certificates from Mozilla. It means that wget and opkg now support fetching resources over HTTPS out-of-the-box. The opkg download server is accessed through HTTPS by default. OpenWrt switched from mbedTLS to wolfSSL as the default SSL library. mbedTLS and OpenSSL are still available and can be installed manually.
In addition, LuCI is now available over HTTPS in addition to HTTP. There is no automatic redirection to HTTPS on a fresh OpenWrt 21.02 installation; however, redirection will be enabled after upgrading from OpenWrt 19.07 to OpenWrt 21.02.
It is always possible to activate or deactivate the redirection to HTTPS like this:
uci set uhttpd.main.redirect_https=1   # 1 to enable redirect, 0 to disable redirect
uci commit uhttpd
service uhttpd reload
Initial DSA support
DSA stands for Distributed Switch Architecture and is the Linux standard to deal with configurable Ethernet switches.
OpenWrt 21.02 comes with initial support for DSA, which replaces the swconfig system that OpenWrt was using up until now. Not all targets have been ported: some devices still use swconfig while some devices already switched to DSA.
This is a significant change to how switch ports and VLANs are managed. As such, sysupgrade will not be able to convert existing swconfig configuration to DSA configuration (see “Upgrading” below).
See the OpenWrt DSA Networking documentation for details.
https://openwrt.org/docs/guide-user/network/dsa/start
The following targets are using a switch managed with DSA in OpenWrt 21.02:
ath79 (only TP-Link TL-WR941ND)
bcm4908
gemini
kirkwood
mediatek (most boards)
mvebu
octeon
ramips (mt7621 subtarget only)
realtek
Increased minimum hardware requirements: 8 MB flash, 64 MB RAM
Due to new features being introduced and the general size increase of the Linux kernel, devices now need at least 8 MB of flash and 64 MB of RAM to run a default build of OpenWrt. More flash space is recommended for extensibility, see 8/64 warning:
https://openwrt.org/supported_devices/864_warning
It is still possible to build custom OpenWrt images (e.g. using the ImageBuilder) that may fit devices with 4 MB of flash or 32 MB of RAM. However, the level of functionality will be reduced and there is no guarantee to stability. See OpenWrt on 4/32 devices for more details and guidance.
https://openwrt.org/supported_devices/openwrt_on_432_devices
New network configuration syntax and board.json change
There have been several changes to the network configuration syntax in /etc/config/network:
in config interface, option ifname has been renamed to device (since it refers to a device section)
in config device of type bridge, ifname has been renamed to ports
for new installs, the generated configuration now creates separate sections for layer 2 (config device) and layer 3 (config interface) configuration
The old syntax is still supported to facilitate transition, and there is no automated migration when upgrading.
However, the LuCI web interface detects old-style configuration and will propose to migrate it to the new syntax. This is necessary to be able to edit network configuration through LuCI.
New UCI syntax
The new configuration style looks like this:
config device
    option name 'br-lan'
    option type 'bridge'
    option macaddr '00:01:02:XX:XX:XX'
    list ports 'lan1'
    list ports 'lan2'
    list ports 'lan3'
    list ports 'lan4'

config interface 'lan'
    option device 'br-lan'
    option proto 'static'
    option ipaddr '192.168.1.1'
    option netmask '255.255.255.0'
    option ip6assign '60'

config device
    option name 'eth1'
    option macaddr '00:01:02:YY:YY:YY'

config interface 'wan'
    option device 'eth1'
    option proto 'dhcp'

config interface 'wan6'
    option device 'eth1'
    option proto 'dhcpv6'
This example uses DSA with lanX interface names. A non-DSA device would use more classical ethX interface names.
Changes to board.json
In addition, network fields in board.json have also been renamed from “ifname” to “device”. In addition, DSA bridges now expose their list of ports in a “ports” attribute.
If you rely on board.json, this change is not backwards compatible.
Example for a DSA bridge:
"network": {
        "lan": {
                "ports": [
                        "lan1",
                        "lan2",
                        "lan3",
                        "lan4"
                ],
                "protocol": "static"
        },
        "wan": {
                "device": "wan",
                "protocol": "dhcp"
        }
}
Example for a classical swconfig switch configuration:
"network": {
        "lan": {
                "device": "eth0",
                "protocol": "static"
        },
        "wan": {
                "device": "eth1",
                "protocol": "dhcp"
        }
}
New hardware targets
A new realtek target has been added, which is often found in managed switches. As a result, it is now possible to run OpenWrt on devices with a significant number of Ethernet ports. See supported devices for realtek.
In addition, new bcm4908 and rockchip targets have been added.
Support for many new boards was added to the existing targets.
Dropped hardware targets
The ar71xx target was deprecated in OpenWrt 19.07 and has been gradually replaced by ath79, see ar71xx-ath79 migration.
https://openwrt.org/docs/techref/targets/ar71xx-ath79
With OpenWrt 21.02, the ar71xx has now been removed and users must use ath79 instead. If you are still running with the ar71xx target, it is recommended to reinstall OpenWrt 21.02 from scratch. Users already on the ath79 target can use sysupgrade to upgrade to OpenWrt 21.02.
Other targets were also removed: cns3xxx, rb532 and samsung.
ASLR activated
Network exposed user space applications are linked as position-independent executable (PIE) to allow full Address Space Layout Randomization (ASLR) support. This makes it harder for attackers to exploit OpenWrt. See Hardening build options for more details.
https://openwrt.org/docs/guide-developer/security#hardening_build_options
Kernel with container support
Multiple Linux kernel compile options, needed for Linux Containers (LXC) and procd-ujail are activated by default for most targets. This allows to use LXC and ujail with the normal release builds.
SELinux support
It is possible to compile OpenWrt with SELinux support. This is currently not activated by default.
Core components update
Core components have the following versions in 21.02.0:
Updated toolchain:
musl libc 1.1.24
glibc 2.33
gcc 8.4.0
binutils 2.34
Updated Linux kernel
5.4.143 for all targets
Network:
hostapd 2020-06-08, dnsmasq 2.85, dropbear 2020.81
cfg80211/mac80211 from kernel 5.10.42
wireguard backport from upstream Linux kernel
System userland:
busybox 1.33.1
In addition to the listed applications, many others were also updated.
Upgrading to 21.02.0
Sysupgrade can be used to upgrade a device from 19.07 to 21.02, and configuration will be preserved in most cases.
Sysupgrade from 18.06 to 21.02 is not supported.
There is no migration path for targets that switched from swconfig to DSA. In that case, sysupgrade will refuse to proceed with an appropriate error message:
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
The default root file system partition size changed for targets/devices relying on booting from mass storage (HDD, USB flash, SD card, etc.), so MBR will change and any additional partition will be deleted when sysupgrading.
Known issues
Some IPv6 packets are dropped when software flow offloading is used:
https://bugs.openwrt.org/index.php?do=details&task_id=3373
As a workaround, do not activate software flow offloading, it is deactivate by default.
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/21.02/notes-21.02.0
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.0#known_issues
For a detailed list of all changes since 19.07 was branched off, refer to:
https://openwrt.org/releases/21.02/changelog-21.02.0
To download the 21.02.0 images, navigate to:
https://downloads.openwrt.org/releases/21.02.0/
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Have fun!
The OpenWrt Community

2 Replies
63

[Assistant]
dmesg shows some problem with mt76 driver:
OpenWrt 21.02.0 Fourth release candidate
Release and security announcements
21.02.0, r16279-5cc0535800 TP-Link Archer C50 v1. Installed as dumb-ap: [ 3328.858879] ------------[ cut here ]------------ [ 3328.863757] WARNING: CPU: 0 PID: 726 at backports-5.10.42-1/net/mac80211/airtime.c:457 0x83556180 [mac80211@be85d16f+0x7c8d0] [ 3328.875308] Modules linked in: rt2800soc rt2800mmio rt2800lib xt_FLOWOFFLOAD rt2x00soc rt2x00mmio rt2x00lib nf_flow_table_hw nf_flow_table nf_conntrack mt76x2e mt76x2_common mt76x02_lib mt76 mac80211 iptable_mangle iptable_filter ipt_REJECT ip…

I’m surprised that x86 isn’t in the list of support for DSA.

1 Reply

Advice for restoring backups from 19.07:
Note that DHCP settings in /etc/config/dhcp have changed for resolvfile.
New value in 21.02 and master is
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
There should be in /etc/config/dhcp:
config dnsmasq
...
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
There is a 19.07 --> 21.02 migration script, but that does not get run if you restore old settings from a backup. (e.g. moving from a ar71xx build to ath79 build, and then restoring 19.07 settings after the initial reboot with 21.02.)

1 Reply
3