[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.1 first service release

Hi,
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 22.03 stable version series. It fixes security issues, improves device support, and brings a few bug fixes.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=22.03.1
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/22.03.1/targets/
Main changes between OpenWrt 22.03.0 and OpenWrt 22.03.1:
Security fixes
wolfssl: Fix security problem (CVE-2022-38152, CVE-2022-38153 and CVE-2022-39173)
See Security Advisory 2022-10-04-1
Device support
Support for the following devices was added:
ZTE MF281
Ubiquiti UniFi FlexHD
Asus RT-AX53U: fix switch setup
GL-inet GL-AP1300: add LTE package, add WAN LED
Ubiquiti XM moved to ath79/tiny
Ubiquiti UniFi 6LR: fix network config
Linksys RE6500: enable LZMA loader to fix boot
LibreRouter v1: fix watchdog and PoE passthrough
NanoPi R4S: ensure unique MAC address
bcm4908:
Enable NVMEM U-Boot env data driver
Backport mtd parser for Broadcom's U-Boot partition
fix -EPROBE_DEFER support in bcm4908_enet
realtek:
fix RTL838x receive tag decoding
fix RTL839x receive tag decoding
ath79/tiny: activate low_mem too
Various fixes and improvements
kernel:
Backport mtd dynamic partition patch
Fix possible mtd NULL pointer dereference
hostapd: rename hostapd multicast_to_unicast option to
multicast_to_unicast_all
mt7620 wifi: multiple improvements
build system:
Switch from xxd tool to xxdi.pl script
Check TLS certificates by default when downloading over HTTPS
Fix issues with targets installed via feeds
Fix build warnings with grep-3.8
Fix build problems with external toolchains
Activate fortify source when using external toolchain
Core components update
Update Linux kernel from 5.10.138 to 5.10.146
Update mt76 from 2022-08-26 to 2022-09-06
Update wolfssl from 5.4.0 to 5.5.1
Update wireless-regdb from 2022.06.06 to 2022.08.12
Update intel-microcode from 20220510 to 20220809
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.1
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/22.03/notes-22.03.1#known_issues
For a detailed list of all changes since 22.03.0, refer to
https://openwrt.org/releases/22.03/changelog-22.03.1
To download the 22.03.1 images, navigate to:
https://downloads.openwrt.org/releases/22.03.1/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=22.03.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

1 Reply
12

[Assistant]
Is https-dns-proxy confirmed working on this release?

2 Replies

"Unsupported version: 22.03.1" for WAX202 on the firmware selector.

2 Replies
1

https://downloads.openwrt.org/releases/22.03.1/targets/ramips/mt7621/openwrt-22.03.1-ramips-mt7621-netgear_wax202-squashfs-factory.img
https://downloads.openwrt.org/releases/22.03.1/targets/ramips/mt7621/openwrt-22.03.1-ramips-mt7621-netgear_wax202-squashfs-sysupgrade.bin

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 24.10.0-rc2 - Second release candidate

Hi,
The OpenWrt community is proud to announce the second release candidate of the upcoming OpenWrt 24.10 stable series.
OpenWrt 24.10.0-rc2 incorporates over 5100 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://openwrt.github.io/firmware-selector-openwrt-org?version=24.10.0-rc2
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/24.10.0-rc2/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-rc1 and 24.10.0-rc2
Fixed opkg installation of kernel modules. The path to the kernel module packages was fixed.
For a detailed list of changes since OpenWrt 24.10.0-rc2 see the 24.10.0-rc2 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.
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 build
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-rc2:
Updated toolchain:
musl libc 1.2.5
glibc 2.38
gcc 13.3.0
binutils 2.42
Updated Linux kernel
6.6.63 for all targets
Network:
hostapd master snapshot from September 2024, dnsmasq 2.90, dropbear 2024.86
cfg80211/mac80211 from kernel 6.11.2
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.
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 forum. 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.
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.0-rc2
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.0-rc2#known_issues
For a detailed list of all changes since 24.10.0-rc1, refer to
https://openwrt.org/releases/24.10/changelog-24.10.0-rc2
To download the 24.10.0-rc2 images, navigate to:
https://downloads.openwrt.org/releases/24.10.0-rc2/targets/
Use OpenWrt Firmware Selector to download:
https://openwrt.github.io/firmware-selector-openwrt-org?version=24.10.0-rc2
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

3 Replies
21

[Assistant]
I've just installed 24.10.0-rc2 on a spare Meraki MR42. It boots fine but when I run a wifi channel analysis I see the following errors in the log. Not sure if they are important. Maybe someone with more knowledge can tell?
Tue Dec  3 11:43:46 2024 kern.warn kernel: [  150.290497] ath10k_pci 0001:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
Tue Dec  3 11:43:46 2024 kern.warn kernel: [  150.290570] ath10k_pci 0001:01:00.0: msdu-desc: 2500  skid: 32
Tue Dec  3 11:43:46 2024 kern.info kernel: [  150.367403] ath10k_pci 0001:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
Tue Dec  3 11:43:46 2024 kern.info kernel: [  150.368131] ath10k_pci 0001:01:00.0: wmi print 'free: 31080 iram: 23028 sram: 9596'
Tue Dec  3 11:43:47 2024 kern.info kernel: [  150.751342] ath10k_pci 0001:01:00.0: rts threshold -1
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.752368] ath10k_pci 0001:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.755473] ------------[ cut here ]------------
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.766398] WARNING: CPU: 0 PID: 817 at backports-6.11.2/net/mac80211/main.c:272 0xbf17a888 [mac80211@869cc7c0+0x77000]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.771107] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_inet ath10k_pci(O) ath10k_core(O) ath(O) pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mac80211(O) cfg80211(O) slhc nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ina2xx crc_ccitt compat(O) at24 sha512_arm seqiv geniv cmac leds_tlc591xx regmap_i2c leds_gpio xhci_hcd dwc3 sd_mod scsi_mod scsi_common ehci_hcd gpio_button_hotplug(O) crc32c_generic
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.819857] CPU: 0 PID: 817 Comm: rpcd Tainted: G           O       6.6.63 #0
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.842022] Hardware name: Generic DT based system
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.849145] Function entered at [<c030d7e8>] from [<c0308f50>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.853828] Function entered at [<c0308f50>] from [<c0a5e94c>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.859644] Function entered at [<c0a5e94c>] from [<c031d364>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.865459] Function entered at [<c031d364>] from [<c031d4e4>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.871276] Function entered at [<c031d4e4>] from [<bf17a888>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.877101] Function entered at [<bf17a888>] from [<bf17a9dc>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.882908] Function entered at [<bf17a9dc>] from [<c08787d4>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.888725] Function entered at [<c08787d4>] from [<c0878c38>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.894540] Function entered at [<c0878c38>] from [<c0878cd0>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.900354] Function entered at [<c0878cd0>] from [<c094869c>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.906172] Function entered at [<c094869c>] from [<c094aeec>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.911988] Function entered at [<c094aeec>] from [<c084abe8>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.917804] Function entered at [<c084abe8>] from [<c04c5564>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.923620] Function entered at [<c04c5564>] from [<c0300060>]
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.929434] Exception stack(0xc240ffa8 to 0xc240fff0)
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.935253] ffa0:                   00000008 bec0eb4c 00000008 00008914 bec0eb4c bec0eb40
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.940377] ffc0: 00000008 bec0eb4c b6eddb79 00000036 bec0ec34 bec0ec4c bec14ca4 00000018
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.948536] ffe0: b6fc2f74 bec0ea10 b6ed6b90 b6f7b704
Tue Dec  3 11:43:47 2024 kern.warn kernel: [  150.956780] ---[ end trace 0000000000000000 ]---
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  162.790095] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  162.790136] ath10k_pci 0000:01:00.0: msdu-desc: 2500  skid: 32
Tue Dec  3 11:43:59 2024 kern.info kernel: [  162.866117] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
Tue Dec  3 11:43:59 2024 kern.info kernel: [  162.866854] ath10k_pci 0000:01:00.0: wmi print 'free: 31080 iram: 23028 sram: 9596'
Tue Dec  3 11:43:59 2024 kern.info kernel: [  163.217199] ath10k_pci 0000:01:00.0: rts threshold -1
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.217801] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.221231] ------------[ cut here ]------------
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.232226] WARNING: CPU: 1 PID: 817 at backports-6.11.2/net/mac80211/main.c:272 0xbf17a888 [mac80211@869cc7c0+0x77000]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.237001] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_inet ath10k_pci(O) ath10k_core(O) ath(O) pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mac80211(O) cfg80211(O) slhc nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ina2xx crc_ccitt compat(O) at24 sha512_arm seqiv geniv cmac leds_tlc591xx regmap_i2c leds_gpio xhci_hcd dwc3 sd_mod scsi_mod scsi_common ehci_hcd gpio_button_hotplug(O) crc32c_generic
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.285711] CPU: 1 PID: 817 Comm: rpcd Tainted: G        W  O       6.6.63 #0
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.307855] Hardware name: Generic DT based system
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.314975] Function entered at [<c030d7e8>] from [<c0308f50>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.319660] Function entered at [<c0308f50>] from [<c0a5e94c>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.325479] Function entered at [<c0a5e94c>] from [<c031d364>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.331293] Function entered at [<c031d364>] from [<c031d4e4>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.337108] Function entered at [<c031d4e4>] from [<bf17a888>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.342926] Function entered at [<bf17a888>] from [<bf17a9dc>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.348740] Function entered at [<bf17a9dc>] from [<c08787d4>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.354558] Function entered at [<c08787d4>] from [<c0878c38>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.360373] Function entered at [<c0878c38>] from [<c0878cd0>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.366187] Function entered at [<c0878cd0>] from [<c094869c>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.372005] Function entered at [<c094869c>] from [<c094aeec>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.377820] Function entered at [<c094aeec>] from [<c084abe8>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.383637] Function entered at [<c084abe8>] from [<c04c5564>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.389454] Function entered at [<c04c5564>] from [<c0300060>]
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.395268] Exception stack(0xc240ffa8 to 0xc240fff0)
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.401085] ffa0:                   00000008 bec0eb4c 00000008 00008914 bec0eb4c bec0eb40
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.406209] ffc0: 00000008 bec0eb4c b6eddb79 00000036 bec0ec34 bec0ec4c bec14ca4 00000018
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.414368] ffe0: b6fc2f74 bec0ea10 b6ed6b90 b6f7b704
Tue Dec  3 11:43:59 2024 kern.warn kernel: [  163.422607] ---[ end trace 0000000000000000 ]---

1 Reply

Flashed rc2 on my GL-MT6000. Added lots of packages and config tweaks it's working awesome.
Only con I'm seeing so far is some instances of daemon.err noted in 16680 though.
Thanks devs!

2

I still don't have the 5GHz band on the TP-Link Archer C60 v1 and other devices. Reported here.

1 Reply
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 22.03.7 seventh service release

Hi,
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 22.03 stable version series. It fixes security issues, improves device support, and brings a few bug fixes.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=22.03.7
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/22.03.7/targets/
OpenWrt 22.03 is EOL
The OpenWrt 22.03 series is end of life according to the OpenWrt security policy. The last release from the OpenWrt 22.03 series is 22.03.7, after this date we will not provide any updates for OpenWrt 22.03, not even for severe security problems. We encourage everyone to upgrade to OpenWrt 23.05 which will be supported till 2025.
Main changes between OpenWrt 22.03.6 and OpenWrt 22.03.7:
Security
CVE-2023-52160: hostapd: Fix a authentication bypass problem in WPA Enterprise client mode.
CVE-2023-36328: dropbear: libtommath: possible integer overflow
CVE-2023-48795: dropbear: implement Strict KEX mode
Device support
ath79: TP-Link TL-WDR3600 and TL-WDR4300: fix spurious reboot hangs
ath79: Ubiquity Bullet M (XW): Fix Ethernet PHY link up
bcm47xx: Linksys WRT320N v1: Fix switch setup
ramips: Improve reliability of bootup by improving reset handling
sunxi: Olinuxino Micro: fix network bringup
Various fixes and improvements
mac80211: add missing config for third 160MHz width for 5GHz radio
hostapd: fix 11r defaults when using SAE
hostapd: fix 11r defaults when using WPA
Core components update
Update Linux kernel from 5.10.201 to 5.10.221
Update ksmbd from 3.4.7 to 3.5.0
Update mac80211 from 5.15.92-1 to 5.15.162-1
Update wolfssl from 5.6.4 to 5.7.2
Update mbedtls from 2.28.5 to 2.28.8
Update wireless-regdb from 2023.09.01 to 2024.07.04
Update intel-microcode from 20230808 to 20240531
Update jsonfilter from 2018-02-04 to 2024-01-23
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.7
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/22.03/notes-22.03.7#known_issues
For a detailed list of all changes since 22.03.6, refer to
https://openwrt.org/releases/22.03/changelog-22.03.7
To download the 22.03.7 images, navigate to:
https://downloads.openwrt.org/releases/22.03.7/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=22.03.7
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

11

[Assistant]
Just updated a Linksys MR8300 using attended sysupgrade with no issues.
Thank you to the team!

1

Is it known whether this release is also affected by the mac80211 wifi throughput issue seen in the recent v23 release?

rseiler:
whether this release is also affected by the mac80211 wifi throughput issue
Likely not.
Mac80211 in 22.03 is based on kernel 5.15 backports, which has not got the problematic commit.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/net/mac80211/cfg.c?h=v5.15.164
23.05 mac80211 is based on kernel 6.1 backports, and there the problem commit exists.
"set station RX-NSS on reconfig"
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/net/mac80211/cfg.c?h=v6.1.102
Two upstream fixes were merged for 23.05, but they are likely not needed for 22.03 (at least not needed for the same reason...)

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.1 First service release

Hi,
The OpenWrt community is proud to announce the first service release of OpenWrt 21.02. It fixes security issues, improves device support, and brings a few bug fixes.
Main changes from OpenWrt 21.02.0
Major bug fixes
Fix Let's Encrypt certificate handling in WolfSSL
Fix sysupgrade for Mikrotik targets
Fix sysupgrade for Rockchip target when using squashfs
Device support
Add support for iEi Puzzle-M901/Puzzle-M902
Various fixes and improvements
Add build system support for Python 3.10
Fix which handling on Fedora and MacOS build systems
Add Tmux terminfo
Core components
Update Linux kernel from 5.4.143 to 5.4.154
Update mac80211 from 5.10.42 to 5.10.68
Update ath10k-ct to 2021-09-22
Update wolfssl from 4.7.0 to 4.8.1
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.
The menu bar in LuCI is wrongly aligned
If this is a real problem for you update the LuCI theme: opkg upgrade luci-theme-bootstrap
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/21.02/notes-21.02.1
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.1#known_issues
For a detailed list of all changes since 21.02.0, refer to
https://openwrt.org/releases/21.02/changelog-21.02.1
To download the 21.02.1 images, navigate to:
https://downloads.openwrt.org/releases/21.02.1/
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

36

[Assistant]
Other than using approx. 20% more memory with the same (21.02.0) packages and configs, and issues with the ATH10K-CT drivers (replaced with the standard ATH10K set), so far so good.
Archer C7 V2

1 Reply
2

Thanks to the dev team for getting this out!
I have installed the update on 3 devices, all successful!
Ubiquiti RouterStation Pro (ath79) -- fixes an ethernet port speed regression that was present in 21.02.0!
TP-Link TL-WR902AC (ath79) -- everything working well
Linksys E3000 (br47xx) -- this is my test/development unit to play with routing/firewall settings and other packages. I don't use wifi on this device.

Thank you very much!
It's great to see the wolfssl (Let's Encrypt) issues solved. I can go back to a smaller image without OpenSSL now on routers that are almost running out of flash space.
Edit: oops... ended up replying to the wrong post.


[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.4 fourth 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, improves device support, and brings a few bug fixes.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=21.02.4
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/21.02.4/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.3 and OpenWrt 21.02.4:
Security fixes
wolfssl: Fix security problem (CVE-2022-34293, CVE-2022-38152, CVE-2022-38153 and CVE-2022-39173)
See Security Advisory 2022-10-04-1
zlib: Fix security problem (CVE-2022-37434)
openssl: Fix security problem (CVE-2022-1292, CVE-2022-2068 and CVE-2022-2097)
Device support
Support for the following devices was added:
Wavlink WL-WN579X3
Sitecom WLR-4100 v1 002
Banana Pi M2 Berry
YunCore AX820/HWAP-AX820
MikroTik RouterBOARD hAP ac lite
MikroTik RouterBOARD mAP
Youku YK1: speed up spi frequency for YK-L1, split YK1 to YK-L1 and YK-L1c
ZBTLink ZBT-WG2626: add reset GPIO for PCIe port 1
ZBTLink ZBT-WE1026 5G: fix watchdog reset
Asus RT-AC57U: fix WPS button level
Archer VR2600: fix switch ports numbering
ZyXEL NBG-419N v2: Fix booting
Linksys MR8300: add WAN port
ramips: several fixes and improvements to mt7620 Ethernet
bcm53xx:
Disable GRO by default at kernel level
Enable & setup packet steering
ipq40xx: fix ar40xx driver
bcm4908:
Enable NVMEM U-Boot env data driver
Backport mtd parser for Broadcom's U-Boot partition
fix -EPROBE_DEFER support in bcm4908_enet
Various fixes and improvements
kernel:
Fix IPv6 flow offloading (FS#3373)
Backport LEDs driver for BCMBCA devices
Backport mtd dynamic partition patch
Fix possible mtd NULL pointer dereference
mac80211: fix QCA9561 PA bias
mac80211: disable ft-over-ds by default
mt76: backport fix encap offload ethernet type check
hostapd fixes and improvements:
Add support for enabling link measurements
Fix uninitialized pointer
zlib: backport null dereference fix
build system:
Switch from xxd tool to xxdi.pl script
Check TLS certificates by default when downloading over HTTPS
feeds: use git-src-full to allow Git versioning
Fix build warnings with grep-3.8
Add compatibility with Python 3.11
Core components
Update Linux kernel from 5.4.188 to 5.4.215
Update openssl from 1.1.1n to 1.1.1q
Update wolfssl from 5.2.0 to 5.5.1
Update wireless-regdb from 2021.08.28 to 2022.08.12
Update intel-microcode from 20210608 to 20220809
Update exfat from 5.12.3 to 5.19.1
Update iwinfo from 2021-04-30 to 2022-04-26
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/21.02/notes-21.02.4
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.4#known_issues
For a detailed list of all changes since 21.02.3, refer to
https://openwrt.org/releases/21.02/changelog-21.02.4
To download the 21.02.4 images, navigate to:
https://downloads.openwrt.org/releases/21.02.4/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=21.02.4
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

3

[Assistant]
FYI, the second URL has a typo (both this forum post and the source wiki page.
https://downloads.openwrt.org/releases/21.04.4/targets/
                                          ^^

There was no reason to think that it was fixed, but just a note here to mention that the cool "reboot and get a new WAN IP most of the time" problem (certain network interface commands can also do it) is still around for those susceptible to the problem (some aren't, for whatever reason).
This problem began in v21. Unsure if it's around in v22 but I would expect so.

I take it that you are referring to routers, such as tp-link Archer C2600?


[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 @ BattleMesh V14

OpenWrt supports this year's "Wireless Battle of the Mesh - Building Community Networks for Fun and Non-Profit".
The event aims to bring together people from across the globe who are interested in community networks, including wireless mesh network technologies, fiber infrastructure, Do-It-Yourself Internet Access Providers, and more generally how to create and maintain a thriving community of people involved in building their own networks.
We envision 4 days of expert presentations, practical workshops, hacking sessions, and fruitful discussions: whether you are a mesh networking enthusiast, community networking activist, protocol developer, or have an interest in networking in general, come and join the event!
The Battlemesh is free of charge and open for all.
This year, the event will take place from Monday 19th to Wednesday 22nd of September, 2022 in Rome, Italy! It will be followed by the RomHack Camp on September 23-25, also in Rome. Check out more information at https://www.battlemesh.org/BattleMeshV14
OpenWrt participated in the Battlemesh v13 online edition in 2020.
We do not have an OpenWrt conference, mostly because organizing such an event is a lot of none technical work.
BattleMesh V14 will not be an official OpenWrt conference, but it would be nice to meet the OpenWrt community in Rome. We can still hack on hardware, drink some beer and talk about OpenWrt and other topics. If you are interested in giving a talk or a workshop about a topic related to OpenWrt, please propose it for Battlemesh V14.
If you do not want to organize a place to stay on your own you have to book the accommodation package, BEFORE Monday, July 11, 2022: https://fusolab.net/battlemesh

1 Reply
12

[Assistant]
hauke:
We do not have an OpenWrt conference, mostly because organizing such an event is a lot of none technical work.
I fully understand.
Are you guys at FOSDEM usually?

Will the presentations be live streamed for those of us who don't want to melt despite the opportunity to eat nice pizza and drink nice perroni?

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 19.07.6 service release

Hi,
The OpenWrt community is proud to announce the sixth service release of OpenWrt 19.07. It focuses on fixing several security issues.
Main changes from OpenWrt 19.07.5
Security fixes
Security Advisory 2021-01-19-1 - dnsmasq multiple vulnerabilities (CVE-2020-25681, CVE-2020-25682, CVE-2020-25683, CVE-2020-25687, CVE-2020-25684, CVE-2020-25685 and CVE-2020-25686)
openssl: NULL pointer deref in GENERAL_NAME_cmp function can lead to a DOS attack. (CVE-2020-1971)
Various security fixes in packages
Note: security fixes for most packages can also be applied by upgrading only the affected packages on running devices, without the need for a full firmware upgrade. This can be done with opkg update; opkg upgrade the_package_name or through the LuCI web interface.
Nevertheless, we encourage all users to upgrade their devices to OpenWrt 19.07.6 or later versions whenever possible.
Major bug fixes
Fix iOS 14 tethering problem
Device support
Enable LED VCC for Asus RT-AC51U
LuCI web interface
luci-mod-system: properly handle SSH pubkeys with options (GH#4684)
luci-mod-network: properly handle wireless netdevs when creating interfaces
Update translations from weblate
Several additional bug fixes and improvements
Core components
Update Linux kernel from 4.14.209 to 4.14.215
Update mac80211 and wifi drivers from 4.19.137-1 to 4.19.161-1
Update wireless-regdb from 2019.06.03 to 2020.11.20
Update mbedtls from 2.16.8 to 2.16.9
Update openssl from 1.1.1h to 1.1.1i
Full release notes and upgrade instructions are available, as well as a detailed list of all changes since 19.07.5 . 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.6 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

22

[Assistant]
Did an imagebuild 19.07.6 with packages and config files on a WRT3200acm from 19.07.5
Not keeping settings offcourse.
Up and running under a minute. Perfect work.

Just updated 2x R7800 and an Archer C7 from .05 to .06. Works perfect.
Thanks for your hard work.

Upgraded ER-X from 19.07.5 to 19.07.6. No issues. Works great.
Amazingly fast response to new security issues! Thank you Developers!
Edit: As of Jan 27 2021 07:30 EST, I upgraded dnsmasq (and only dnsmasq) to 2.80-16.3 after 19.07.6 installation and can also report this is working fine with no issues. I did not notice any issues prior, but it seemed prudent to grab this update given reports of others.

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: Project statement about xz 5.6.1 (CVE-2024-3094)

Hi,
tl;dr OpenWrt seems to be not affected by the CVE-2024-3094
As you may be aware, malicious code was identified in the xz upstream tarballs starting from version 5.6.0. The development snapshots of OpenWrt were utilizing this compromised library version.
Fortunately, the snapshots builds relied on source code tarballs from GitHub releases, which are generated automatically. These contained only the dormant segment of the malicious code. The crucial component that would activate the backdoor during the build process was not detected in the scrutinized tarball archives.
For those interested, the source tarballs employed in the official OpenWrt snapshot builds are still accessible:
http://sources.openwrt.org/xz-5.6.1.tar.xz.backdoored
(sha256sum: d300422649a0124b1121630be559c890ceedf32667d7064b8128933166c217c8)
http://sources.openwrt.org/xz-5.6.1.tar.bz2.backdoored
(sha256sum: f334777310ca3ae9ba07206d78ed286a655aa3f44eec27854f740c26b2cd2ed0)
Binary packages built using affected xz sources can be downloaded from https://mirror-03.infra.openwrt.org/snapshots/packages/xz-5.6.1-ipks.tar.gz (sha256sum: a376b30cc8afe2ebf92316b47c640e845cd76bef4f2c593ca22e6fc12deb580d).
Timeline
March 29, 2024 10:17 AM Started investigating the issue
March 29, 2024 10:59 AM Reverting the xz 5.6.1 package version bumps
March 29, 2024 11:11 AM Moved affected sources/packages to .backdoored file suffixes on downloads.openwrt.org and sources.openwrt.org servers
March 29, 2024 1:08 PM CDN cache invalidated as well
Happy Easter!

4 Replies
45

[Assistant]
<soapbox_mode=on>
I'll add that this incident reinforces my belief that an edge device should have minimum complexity and attack surface. In other words, don't get a big x86 box, run some VM host on it and make your gateway an OpenWrt VM/container on that device. Keep that perimeter simple and clean, folks, the less stuff you potentially expose the better...

1 Reply
11

For those who are curious, here's the best write-up I've read thus far.
gist.github.com
https://gist.github.com/thesamesam/223949d5a074ebc3dce9ee78baad9e27
xz-backdoor.md
# FAQ on the xz-utils backdoor

## Background

On March 29th, 2024, a backdoor was discovered in
[xz-utils](https://xz.tukaani.org/xz-utils/), a suite of software that
gives developers lossless compression. This package is commonly used
for compressing release tarballs, software packages, kernel images,
and initramfs images. It is very widely distributed, statistically
your average Linux or macOS system will have it installed for
This file has been truncated. show original

6

Out of pure curiosity, does xz-utils have sponsors, is this another case of an open source project solely relying on contributors working in their free time?

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: OpenWrt 18.06.9 final service release

Hi,
The OpenWrt Community is proud to announce the ninth service release of the stable OpenWrt 18.06 series. OpenWrt 18.06.9 brings security fixes, as well as the usual device support fixes and core components update.
End of support for OpenWrt 18.06: This release is the final one for OpenWrt 18.06. You should consider upgrading to a newer version (OpenWrt 19.07 or later)
The main 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)
Security Advisory 2020-05-06-2 - relayd out-of-bounds reads of heap data and possible buffer overflow (CVE-2020-11752)
Security Advisory 2020-05-06-1 - umdns out-of-bounds reads of heap data and possible buffer overflow (CVE-2020-11750)
ibjson-c: fix out of bounds write vulnerability (CVE-2020-12762)
mac80211: backport some fixes for the Kr00k vulnerability in WPA. It is not clear which wireless driver/firmware combinations could be vulnerable in OpenWrt. These backported patches harden mac80211 just in case.
Other security fixes
Note: security fixes for most packages can also be applied by upgrading only the affected packages on running devices, without the need for a full firmware upgrade. This can be done with opkg update; opkg upgrade the_package_name or through the LuCI web interface.
Nevertheless, we encourage all users to upgrade their devices to OpenWrt 18.06.9 or a newer major release whenever possible.
Bug fixes
libubox: Fix regression that could cause procd to fail to start or restart some services. This is especially visible as it broke LuCI when upgrading from older 18.06.X releases
musl: fix locking synchronization bug
kernel: backport out-of-memory fix for non-Ethernet devices
firewall: fix TCP MSS clamping that was only applied on one direction
Device support
brcm63xx: fix BCM6348/BCM6358 hangs while booting
ipq40xx: fix essedma MAC hang by disabling TCP segmentation offload for IPv6
ramips: fix USB detection on all rt305x devices
mikrotik: add support for the new ath9k caldata encoding (LZO) found in newer hardware revisions
Various fixes for ZyXEL Keenetic, ZyXEL NBG6616, TP-Link Archer C60 v1/v2, GL.iNet GL-AR750S, Embedded Wireless Dorin, Pirelli A226M-FWB, Arduino Yun
Core components update
Linux kernel updated from 4.9.214 to 4.9.243 and from 4.14.171 to 4.14.206
mbedtls updated from 2.16.4 to 2.16.8
wireguard updated from 0.0.20190601 to 1.0.20200611
Additional notes
Full release notes and upgrade instructions are available, as well as a detailed list of all changes since 18.06.8.
To download a OpenWrt 18.06.9 firmware image for your device, 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

7

[Assistant]
I'm wondered that why Archer C20 V5 is not in that list for both 18.06. and 19.07 and someone should compile it

Support for the TP-Link Archer C20 v5 has only been added to master in january 2020, way after openwrt-18.06 or openwrt-19.07 had been branched off. This device will be part of the next major OpenWrt release (20.xy.0, respectively 21.xy.0 at this point), but won't be backported to older service releases.

4

This release on ar71 seems to have the luci bug where if you're on the overview screen the load average starts climbing rapidly. Bug does not exist at this level in previous versions of 18.06


[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.2 - 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.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=23.05.2
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/23.05.2/targets/
Main changes between OpenWrt 23.05.0 and OpenWrt 23.05.2
23.05.1 was tagged, but not officially released because we found a severe bug between tagging and announcing the release.
Device support
Support for the following devices was added:
* bcm53xx: ASUS RT-AC3100
* mediatek: CMCC RAX3000M
* mediatek: MT7981 RFB
* ramips: ComFast CF-E390AX
* ramips: ComFast CF-EW72 V2
* ramips: MeiG SLT866 4G CPE
* realtek: HPE 1920-8g-poe+ (65W)
apm821xx: Netgear WNDR4700: Fix broken sysupgrade, factory images
armsr: Preserve configuration during sysupgrade
ath79: Compex wpj563: Enable 2nd USB controller
ath79: TP-Link Archer C7 v2: Fix wifi shutdown and "irq 23: nobody cared" error
bcm53xx: Make Linux use correct switch ports again
bcm53xx: Linksys EA9200: nvram and 02_network fixes
ipq40xx: Switch to performance governor by default
lantiq: xrx200: Build target again
mediatek: Xiaomi Redmi Router AX6000: Fix Ethernet in U-Boot
realtek: HPE 1920-8g-poe: Rename to match hardware
ramips: HiWiFi HC5861: Fix Gigabit Ethernet port
ramips: ZyXEL NR7101: Fix bricking typo
Various fixes and improvements
Fix assignment of default MAC addresses on some targets
build: Hide kmod-zram config unless enabled
build: Fix lto build
build: Fix glibc build
build: Fix pkg-config detection when inside of a nix-shell
build: Add CycloneDX SBOM JSON support
hostapd: Do not trim trailing whitespace, except for newline
hostapd: Fix OWE association with mbedtls
hostapd: Fix broken WPS on broadcom-wl and ath11k
hostapd: Fix broken noscan option
wifi: Fix applying mesh parameters when wpa_supplicant is in use
iptables: backport patch fixing bug with string module
mbedtls: Activate secp521r1 curve by default
px5g-mbedtls: Fix permission of private key
px5g-wolfssl: Fix permission of private key
netifd: Fixed race condition in default gateway configuration
Core components update
Update mbedtls from 2.28.4 to 2.28.5
Update openssl from 3.0.11 to 3.0.12
Update wolfssl from 5.6.3 to 5.6.4
Update Linux from 5.15.134 to 5.15.137
Update ipq-wifi from 2023-06-03 to 2023-11-10
Update uqmi from 2022-05-04 to 2022-10-20
Update umdns from 2023-01-16 to 2023-10-19
Update urngd from 2023-07-25 to 2023-11-01
Update ucode from 2023-06-06 to 2023-11-07
Update firewall4 from 2023-03-23 to 2023-09-01
Update odhcpd from 2023-06-24 to 2023-10-24
Update netifd from 2023-10-20 to 2023-11-10
Upgrading to 23.05.2
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.2 was signed with the wrong signing keys. The keys from OpenWrt snapshot were used for 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.2#known_issues
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/23.05/notes-23.05.2
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/23.05/notes-23.05.2#known_issues
For a detailed list of all changes since 23.05.0, refer to
https://openwrt.org/releases/23.05/changelog-23.05.2
To download the 23.05.2 images, navigate to:
https://downloads.openwrt.org/releases/23.05.2/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=23.05.2
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
30

[Assistant]
Thanks you very much, Devs and Testers and all others involved, can report, that Attendet Sysupgrade worked well updating 23.05.0 to 23.05.2 on X86. Cheers!

1 Reply

hauke:
OpenWrt 23.05.2 was signed with the wrong signing keys. The keys from OpenWrt snapshot were used for OpenWrt 23.05.2, OpenWrt 23.05.0 and the release candidates. A later OpenWrt 23.05 service release will use a different key.
Is this something to be weary of as a potential conflict during upgrades to/from 23.05.2? Or would it apply moreso to users that are independently verifying signed images, and can be safely disregarded otherwise?

@hauke
,
@nbd
and other devs
Thank you for your awesome work.
I have a concern regarding the netifd package in 23.05.2 release factory and sysupgrade images in https://downloads.openwrt.org/releases/23.05.2/targets/ .
From what I understand, 23.05.2 was tagged right after 23.05.1 release due to "netifd: Fixed race condition in default gateway configuration" (https://github.com/openwrt/netifd/issues/17). The related netifd package bump commit (I think) is https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=842932a63d8993150ff339f11f0cd0d5dc45e6cc which bumped the pkgrel from 1 to to 1.1.
However the Packages Buildbot https://buildbot.staging.openwrt.org/openwrt-23.05/packages/#/builders hasn't yet compiled the netifd pkgrel 1.1 with that fix yet. As an example, I still see netifd pkgrel 1 file (NOT pkgrel 1.1) at https://downloads.openwrt.org/releases/23.05.2/packages/aarch64_cortex-a53/base/netifd_2023-11-10-35facc83-1_aarch64_cortex-a53.ipk (as the packages buildbot for aarch64_cortex-a53 https://buildbot.staging.openwrt.org/openwrt-23.05/packages/#/builders/22 hasn't rebuilt the pkgs yet, after the netifd bump commit).
I have observed that it takes roughly 2 to 3 days from a git commit to the corresponding shared pkgs updated in the repos. I am not sure if the patched netifd pkg (pkgrel 1.1 instead of pkgrel 1) is included in the default factory and sysupgrade images generated by the images buildbot https://buildbot.staging.openwrt.org/images/#/builders .
Also if I use ImageBuilder and / or Attended Sysupgrade to build custom images, will the updated netifd pkg be included in the built images or will imagebuilder pull netifd pkgrel 1 from the repos?

2 Replies
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] Q: Major Change Notice: New Package Manager

[Assistant]
As of November 2024 for snapshots from the main development branch and future stable release builds (possibly also including the upcoming 24.10 series), the package manager in OpenWrt has changed from opkg to apk.
This new package manager offers a number of advantages over the older opkg system and is a significant milestone in the development of the OpenWrt platform. The older opkg package manager has been deprecated and is no longer part of OpenWrt.
As this represents a fundamental shift in the method for installing and managing packages, there is an active discussion in the Talk about Documentation subsection of the forum, including the options and syntax used by this new system.
Note: This change does not affect 23.05.
(And as of 15 Nov 2024, also the 24.10 branch is still using opkg.)

57


[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: Bug tracking has moved to GitHub

On February 9th 2022 at 12:00am CET was bug tracking replaced with https://github.com/openwrt/openwrt/issues.
Due to this decision it’s not possible to login to this system anymore. Old bugs might be migrated to the GitHub issues, but it might take some time. Until then feel free to create new issue at the GitHub issues. We’re sorry for any inconvenience this might cause.
EDIT: fixed GitHub link, copy pasta fail, thanks
@hnyman

23

[Assistant]
I think it may have confirmed-dev only issue that non-login user can't see like exploitable security issue: did they migrated manually?

I think it may have confirmed-dev only issue that non-login user can't see like exploitable security issue: did they migrated manually?
OpenWrt Wiki – 5 Mar 17
Reporting bugs
Reporting bugs Bug or no bug? In case you are unsure if what you found is a bug, or if you have other issues that are not bugs, please use the forum, IRC or mailing list. Issue trackers Report bugs pertaining OpenWrt functionality and device...

1

Request for clarity about submitting bug reports.
I am about to submit a bug report that i believe should be fixed on openwrt.
However, this bug likely affects ath10k (core) and ath10k-ct (a package?).
Where is the appropriate place for bug reports that might affect multiple core components and/or packages?
ty
EDIT0 My proposed "answer" to this is submit the bug report in one place that its applicable to and let you all sort out the rest.
EDIT1 But it might help users to have only place to search for issues and since the dev's will have to delegate out bug reports anyway, why not keep all bug reports in once place?

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: Notice: Problems with custom firmware image creation

2025-Feb-13: There are known intermittent issues generating custom images using the online image generator (firmware selector and sysupgrade servers). This affects Attended Sysupgrade (ASU), OWUT (OpenWrt Upgrade Tool), and the firmware-selector custom image tool. See this thread for more details.
Please do not open new threads on this topic as it has already been discussed in numerous threads (with the same answers each time).

9

[Assistant]
While I cannot speak to the specifics (not my area of expertise), the issue is related to problems in the build system with mismatched checksum/hashes and the like.
In many cases, the errors that are surfacing will include...
 * opkg_install_pkg: Checksum or size mismatch for package
and/or
 * pkg_hash_check_unresolved: cannot find dependency
You may also see a note about "Impossible package selection" and other failures.
These are known issues -- the banner will be removed when it is resolved.
In the meantime... Feel free to refer to the threads where this is already being discussed:
Owut: OpenWrt Upgrade Tool
Community Builds, Projects & Packages
SNAPSHOT+apk blocker list (for easy reference) 24.10 should be fully working as of 2024-11-27. SNAPSHOT should be "working" as of 2024-12-10. Transitions from opkg-based versions (24.10-or-earlier, and older SNAPSHOTs) to apk-based SNAPSHOT are still an issue. They will remain so, as there's no way to fix the older versions without actually updating them. If you are in this situation, please post below and we'll walk you through it. If you see things like these, continue reading... libubus2…
The OpenWrt Firmware Selector
Release and security announcements
We are happy to announce a new service, the OpenWrt Firmware Selector. It allows to easily find a firmware image for your device. Feedback is welcome in this thread!

4

I hope this is fixed for now, I disabled the Squid caching. It caused to use "old" packages, resulting in a checksum mismatch afterwards. I'm investigating how the Squid configuration could be improved. If anyone reading this knows things around Squid, please help me with the configuration.

2 Replies
18

Problems are not gone.
STDERR:

Generate local signing keys...
Generate local certificate...
Package list missing or not up-to-date, generating it.
Building package index...
Downloading https://downloads.openwrt.org/releases/24.10.0/targets/x86/geode/packages/Packages.gz
Updated list of available packages in /builder/build_dir/target-i386_pentium-mmx_musl/root-x86/../../../../builder/dl/openwrt_core
Downloading https://downloads.openwrt.org/releases/24.10.0/targets/x86/geode/packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/24.10.0/packages/i386_pentium-mmx/base/Packages.gz
Updated list of available packages in /builder/build_dir/target-i386_pentium-mmx_musl/root-x86/../../../../builder/dl/openwrt_base
Downloading https://downloads.openwrt.org/releases/24.10.0/packages/i386_pentium-mmx/base/Packages.sig
Signature check passed.
.
.
.
Downloading file:packages/Packages
Updated list of available packages in /builder/build_dir/target-i386_pentium-mmx_musl/root-x86/../../../../builder/dl/imagebuilder
Downloading file:packages/Packages.sig
Signature check passed.
Collected errors:
 * opkg_install_cmd: Cannot install package libavahi-compat-libdnssd
make[2]: *** [Makefile:234: package_install] Error 255
make[1]: *** [Makefile:171: _call_manifest] Error 2
make: *** [Makefile:349: manifest] Error 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 24.10.0 - First Stable Release

Hi,
The OpenWrt community is proud to announce the first stable release of the OpenWrt 24.10 stable series.
OpenWrt 24.10.0 incorporates over 5400 commits since branching the previous OpenWrt 23.05 release and has been under development for over one year.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org?version=24.10.0
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/24.10.0/targets/
Highlights in OpenWrt 24.10
General changes
Upgrades of many components to new versions like the Linux kernel from version 5.15 to 6.6
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 1970 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:
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.
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.
Kernel warning in ath10k-ct driver at startup. The warning WARNING: CPU: 3 PID: 1695 at backports-6.9.9/net/mac80211/main.c:270 ieee80211_do_open+0x4e8/0x5e0 [mac80211] appears during boot but is harmless and can be ignored. See issue #15959 for details.
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.0
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.0#known_issues
For a detailed list of all changes since 24.10.0-rc7, refer to
https://openwrt.org/releases/24.10/changelog-24.10.0
To download the 24.10.0 images, navigate to:
https://downloads.openwrt.org/releases/24.10.0/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=24.10.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

6 Replies
75

[Assistant]
Too bad I have both Belkin RT3200 and Redmi AX6S as well as a bunch of ipq806x. Gonna roll the dice and hope I don't make a mistake

Xiaomi AX3200 image build is broken (worked until RC7). Should be added to known issues and upgrade guide removed. Current image soft-bricks device.

2 Replies
4

Would I lose extroot if I reset and install the firmware?


[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.7 service release

The OpenWrt community is proud to announce the seventh service release of OpenWrt 19.07. It fixes security issues, improves device support, and brings a few bug fixes.
  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 19.07.7, r11306-c4a6851c72
 -----------------------------------------------------
Main changes from OpenWrt 19.07.6
Only the main changes are listed below. See changelog-19.07.7 for the full changelog.
Security fixes
Security Advisory 2021-02-02-1 - netifd and odhcp6c routing loop on IPv6 point to point links (CVE-2021-22161)
Security Advisory 2021-02-02-2 - wolfSSL heap buffer overflow in RsaPad_PSS (CVE-2020-36177)
Various security fixes in packages
Note: security fixes for most packages can also be applied by upgrading only the affected packages on running devices, without the need for a full firmware upgrade. This can be done with opkg update; opkg upgrade the_package_name or through the LuCI web interface.
Nevertheless, we encourage all users to upgrade their devices to OpenWrt 19.07.7 or later versions whenever possible.
Major bug fixes
Fix dnsmasq error messages such as failed to send packet: Network unreachable or failed to send packet: Address family not supported by protocol that could be filling up logs. This was a regression caused by the dnsmasq update in 19.07.6.
Fix opkg so that it purges obsolete packages from its local cache. This fixes a long-standing issue in the ImageBuilder where a manual cleanup was needed before rebuilding: FS#2690
Device support
Improve stability of mediatek Ethernet switch (affects many mt7621 devices): FS#2628
Fix Wi-Fi band detection on some Broadcom-based devices
Fix poor 2.4 GHz Wi-Fi performance on TP-Link Archer C50 v4 due to a missing EEPROM chip ID: FS#2781
Make initramfs image usable out-of-the-box on Turris Omnia
Use full flash size on Nucom R5010UN v2
Fix support for TP-Link TL-WR810N v1 in ath79: FS#3522
Remove broken factory image for TP-Link Archer C2 v1
Fix unintended failsafe mode during boot on Netgear EX6150: FS#3590
Various fixes and improvements
The ImageBuilder no longer requires compilers (gcc, g++) and libncurses-dev. This was partially implemented in 19.07.6 but one part was missing to make it actually work.
Update to a new major version of ksmbd to fix several bugs. This breaks compatibility with previous versions of OpenWrt (19.07.0 to 19.07.6): it is no longer possible to install a working version of ksmbd-tools on previous versions of OpenWrt. Existing installations will keep working, but ksmbd-tools should not be upgraded with opkg. PR#14647
See addressed_bugs for a complete list of bug fixes.
LuCI web interface
Fix array sorting on Chrome: GH#4792
Add nextdns.io and quad 101 providers to luci-app-https-dns-proxy package
Update translations from weblate
Several additional bug fixes and improvements
Core components
Update Linux kernel from 4.14.215 to 4.14.221
Update wolfssl from 4.5.0 to 4.6.0
Regressions
kmod-fs-ksmbd has a dependency to the not existing package kmod-crypto-arc4. Installing kmod-fs-ksmbd returns this:
satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-fs-ksmbd: * kmod-crypto-arc4 * opkg_install_cmd: Cannot install package kmod-fs-ksmbd.
Run this to force the installation: GH#14771
opkg install --force-depends kmod-fs-ksmbd
to force the installation.
Known issues
Transition to ath79: some devices that are supported in ar71xx are not yet supported in ath79: this is a community effort. Helping to port devices to ath79 to make them available in future releases is very welcome.
Device support: images for some device became too big to support a persistent overlay, causing such devices to lose configuration after a reboot. If you experience this problem, please report the affected device in the forum and consider downgrading to OpenWrt 18.06 or using the Image Builder to pack a smaller custom image
Device support: conversely, certain images for devices with small flash (4 MB) are no longer built for the release
See also: active bug reports for openwrt-19.07
Upgrading to OpenWrt 19.07.7
Upgrading from previous OpenWrt 19.07 versions is straightforward thanks to the sysupgrade utility: sysupgrade from web interface or sysupgrade from command-line.
An upgrade from OpenWrt 18.06 to OpenWrt 19.07 is supported in many cases, including preserving configuration. A configuration backup is advised nonetheless when upgrading from OpenWrt 18.06.
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Have fun!
The OpenWrt Community

1 Reply
30

[Assistant]
sysupgrade from 19.07.6 ran smoothly on tp-link archer c6 v2 eu.
Wifi up and running again, family is satisfied, good job, developers

1

Sysupgrade from 19.07.07 on xiaomi r3g v1
Wifi working stable again and bug of dnsmasq solved.
Thanks for working dev's

ER-X upgraded from 19.07.6 to 19.07.7 - all is well after ~2 days of run time. Zero issues.

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: OpenWrt 19.07.9 ninth service release

Hi,
The OpenWrt community is proud to announce the ninth service release of OpenWrt 19.07. It fixes security issues, improves device support, and brings a few bug fixes.
The main changes from OpenWrt 19.07.8 are:
Security fixes
Various security fixes in packages
Major bug fixes
Fix missing includes for SDK
Device support
rb91x: fix 10M ethernet link speed
Core components
Update Linux kernel from 4.14.241 to 4.14.267
Update mac80211 from 4.19.193-1 to 4.19.221
Regressions
The ImageBuilder fails to find a the SOURCE_DATE_EPOCH variable and therefore the profiles.json creation is broken.
To fix this issue export the missing environmental variable before using the ImageBuilder: export SOURCE_DATE_EPOCH=1
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/19.07/notes-19.07.9
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/19.07/notes-19.07.9#regressions
For a very detailed list of all changes since 19.07.8, refer to
https://openwrt.org/releases/19.07/changelog-19.07.9
For latest information about the 19.07 series, refer to the wiki at:
https://openwrt.org/releases/19.07/
To download a OpenWrt 19.07.9 firmware image for your device, head to the Table of Hardware:
https://openwrt.org/toh/start
Or use the new firmware selector:
https://firmware-selector.openwrt.org/
You can also navigate directly in the list of firmware images:
https://downloads.openwrt.org/releases/19.07.9/targets/
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Sunshine!
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

7

[Assistant]
Thank you. Updated TP-Link Archer A7v5 successfully. Is it my imagination or does LUCI seem much faster?

I also have two of these and I am currently running them on master build from last year in mesh mode (and barely able to push 200 mbps via wifi). What sort of bandwidth are you seeing when using this version on wired and wireless (5GHz)?
EDIT: I should note, I have a 300mbps symmetric fiber line where these are being used... the Fiber goes into the ONT and from there I have a CAT5E going into one TP-Link Archer A7v5 (serving as the main router) and the 2nd unit sits on the floor below. I am running mesh because I don't have the ability to run a wired backhaul. 5Ghz band from the main unit gives me about 212mbps up/down. I am pretty sure the stock firmware will be able to push the full 300 up/down.
I'm interested in knowing if this version of 19.07 is capable of pushing the full 300mbps on the 5GHz band.
EDIT2: I also tend to run without Software Flow Offloading. Two reasons:1. I saw no improvement in throughput in my case (perhaps master build at the time was in a limbo state where version 21 was being finalized) and 2. The flow offloading feature interferes with port forwarding (wasn't able download files from my NAS from the WAN until I disabled flow offloading, perhaps it is fixed now).

1 Reply

How long will 19.07.9 be supported?
My understanding is this is the last service release for 19.07.

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: New Wi-Fi vulnerability (probably) affecting OpenWrt

(Should go in security announcements)
https://www.fragattacks.com/
https://lore.kernel.org/linux-wireless/20210511180259.159598-1-johannes@sipsolutions.net/
Patchset at the above link includes patches for mac/cfg80211 and ath10k/ath11k

16

[Assistant]
To master I guess? Will there also be a patch for 19.07.7?

3 Replies
2

ML thread, appears there will be some forthcoming

9

anomeome:
patched up
great job. thanks to the devs
Ramon:
To master I guess?
How do I see the branches in this Web UI https://git.openwrt.org/?p=openwrt/openwrt.git;a=summary
For every release a branch?

2 Replies
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-rc4 - Fourth release candidate

Hi,
The OpenWrt community is proud to announce the fourth release candidate of the upcoming OpenWrt 24.10 stable series.
OpenWrt 24.10.0-rc4 incorporates over 5100 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://openwrt.github.io/firmware-selector-openwrt-org?version=24.10.0-rc4
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/24.10.0-rc4/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-rc2 and 24.10.0-rc4
LuCI had multiple severe bugs in OpenWrt version 24.10.0-rc3, we did not officially released it.
Linux Kernel update to version 6.6.67
Added support for Realtek RTL8812au/RTL8821au USB wifi devices
d1: Renamed boards to match device tree compatible string
lantiq: xrx200_legacy: Create subtarget with less flash usage. Move the following devices to xrx200_legacy:
Alpha ASL56026 / BT Openreach ECI VDSL Modem V-2FUb/I
BT Openreach ECI VDSL Modem V-2FUb/R
NETGEAR DM200
TP-Link Archer VR200 v1
TP-Link Archer VR200v v1
TP-Link TD-W8970 v1
TP-Link TD-W8980 V1
mediatek: filogic: Cudy WR3000: Fix MAC addresses
mediatek: filogic: Migrate wifi configuration device paths
qualcommax: ipq807x: fixed device IDs for some Netgear devices
realtek: Zyxel GS1900: merge firmware partitions
For a detailed list of changes since OpenWrt 24.10.0-rc4 see the 24.10.0-rc4 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-rc4:
Updated toolchain:
musl libc 1.2.5
glibc 2.38
gcc 13.3.0
binutils 2.42
Updated Linux kernel
6.6.67 for all targets
Network:
hostapd master snapshot from September 2024, dnsmasq 2.90, dropbear 2024.86
cfg80211/mac80211 from kernel 6.11.2
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.
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.0-rc4
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.0-rc4#known_issues
For a detailed list of all changes since 24.10.0-rc2, refer to
https://openwrt.org/releases/24.10/changelog-24.10.0-rc4
To download the 24.10.0-rc4 images, navigate to:
https://downloads.openwrt.org/releases/24.10.0-rc4/targets/
Use OpenWrt Firmware Selector to download:
https://openwrt.github.io/firmware-selector-openwrt-org?version=24.10.0-rc4
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
21

[Assistant]
hauke:
TLS 1.3 support in default images
mbedtls was updated to version 3.6 which includes support for TLS 1.3
Is there a way to configure uhttpd to accept only TLS 1.3 connections? I can't find options in the wiki documentation, https://openwrt.org/docs/guide-user/services/webserver/uhttpd

1 Reply

Flashed rc4 on my GL-MT6000. Added my config, lots of settings, and packages. Everything is working great. Thanks for your efforts to all the devs and happy holidays!

14

No, restricting ustreamssl to only TLS 1.3 is not supported, you can add this and create a PR.

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 Summit 2024 & Battlemesh v16 Announcement

Hello everyone!
We're doing an OpenWrt summit this year. We're inviting all OpenWrt enthusiasts to join us at the event. We will auction off one or two OpenWrt One. And we will have a big cake for OpenWrt's 20 year anniversary. It's going to be a relaxed event full of social activities with visits to very special places.
Date: 18-19 May 2024, 2 days
Venue: Tatlısu/Ακάνθου/Akanthou, Cyprus
We're also hosting the Battlemesh v16 event starting 15 May 2024. We have visits to very special places on 15 and 19 May. I suggest arriving in Cyprus on 14 May and departing on 20 May. The event is free of charge and open for all.
Registering:
Add yourself to the participants list. I will use the participants list to fill the visit request form to enter the Nicosia airport, read the event page below for more information. If you'd rather not have your name there, please send an email to the organisation team with the same information displayed on the participants list.
https://www.battlemesh.org/BattleMeshV16/Participants
Accomodation Package:
We've agreed on a discounted price with the Olive Tree Hotel. Single room 60€ per night, double room 80€ per night. Breakfast and dinner is included.
The hotel guarantees availability to host 50 people for a 6-night stay; check-in on 14 May and check-out on 20 May. Please make a reservation by adding yourself to the participants list two days prior to your check-in date.
Taking the accomodation package is, of course, optional.
For those coming from abroad, we suggest you arrive to Larnaca International Airport.
More information:
https://www.battlemesh.org/BattleMeshV16
Please help us spread the word by sharing this announcement.
Arınç

13

[Assistant]
Is this an official OpenWrt event? Organizing such events in places with a troublesome status like northern part of Cyprus seems questionable for me.

2 Replies
4

We've decided that the northern part of Cyprus will be a part of the locations for Battlemesh v16 & OpenWrt Summit 2024 on Battlemesh v15 in May 2023, with Hauke's presence. We also explain the sitaution in Cyprus in detail on the Battlemesh v16 page and ensure the event will traverse safely. Hauke has approved this announcement.

3

This is an office OpenWrt event. Thank you Arınç for organizing it.

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 moves its IRC presence to OFTC

Hi,
Following a vote among project members on May 26th, it has been decided
that OpenWrt moves its official IRC presence to the OFTC network.
To learn about how to connect or register on OFTC, refer to the network's
homepage at https://www.oftc.net/.
You can find the most up-to-date information about OpenWrt's IRC presence at
https://openwrt.org/irc.
Kind regards,
Jo

9

[Assistant]
Don't forget that we also have a Matrix room:
https://matrix.to/#/#OpenWrt:matrix.org?via=grin.hu&via=matrix.org&via=systemtest.tk

1

has this decision something to do with the witch hunt described here?
It's FOSS News – 21 May 21
Open Source World's Favorite IRC Network Freenode is in Turmoil - It's FOSS News
In the last couple of days, there's been quite a bit of drama and turmoil taking place around Freenode.
Est. reading time: 6 minutes

2

Naftali:
has this decision something to do with the witch hunt described here?
Freenode simply has lost the trust of a few projects to operate one of their communication channels, OpenWrt is one of them.

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]
Title: Security Advisory 2022-10-17-1 - Multiple issues in mac80211 and cfg80211 (CVE-2022-41674, CVE-2022-42719, CVE-2022-42720, CVE-2022-42721 and CVE-2022-42722)

DESCRIPTION
Multiple vulnerabilities were found in the Linux Kernel mac80211 and cfg80211 framework. OpenWrt takes the mac80211 and cfg80211 framework from the wireless backports project which copies it from a more recent Linux kernel version.
These vulnerabilities are in the multi BSSID (MBSSID) beacon parsing code and the P2P-device beacon parsing code.
CVE-2022-41674 [0]: fix u8 overflow in cfg80211_update_notlisted_nontrans (max 256 byte overwrite) (RCE)
CVE-2022-42719 [1]: wifi: mac80211: fix MBSSID parsing use-after-free use after free condition (RCE)
CVE-2022-42720 [2]: wifi: cfg80211: fix BSS refcounting bugs ref counting use-after-free possibilities (RCE)
CVE-2022-42721 [3]: wifi: cfg80211: avoid nontransmitted BSS list corruption list corruption (DOS)
CVE-2022-42722 [4]: wifi: mac80211: fix crash in beacon protection for P2P-device NULL ptr dereference crash (DOS)
REQUIREMENTS
The vulnerabilities are mostly in the Wifi beacon parsing code. OpenWrt operating as Wifi AP or Wifi client is affected when it scans for Wifi networks. A malicious attacker could exploit this by sending specially crafted packets while the target is scanning for Wifi networks. A malicious attacker has to be physically close to the target to exploit these vulnerabilities. This can be exploited by attackers which are not necessary part of the network, no authentication needed. Wifi drivers in OpenWrt will parse beacons from arbitrary Wifi devices nearby.
All Wifi drivers in OpenWrt are using cfg80211 and many are using mac80211.
MITIGATIONS
You need to update to a fixed OpenWrt version. Fixes for the vulnerabilities are integrated in OpenWrt 22.03.2 and OpenWrt 21.02.5. Upgrading the packages with opkg update is not sufficient.
The fix is contained in the following and later versions:
OpenWrt master: 2022-10-13 (fixed by reboot-20925-g26f400210d6b)
OpenWrt 22.03: 2022-10-13 (fixed by v22.03.1-16-gf1de43d0a0)
OpenWrt 21.02: 2022-10-13 (fixed by v21.02.4-2-gfa9a932fdb)
AFFECTED VERSIONS
To our knowledge, OpenWrt snapshot images are affected. OpenWrt stable release versions 22.03.1 and OpenWrt 21.02.4 and earlier are affected. Older versions of OpenWrt (e.g. OpenWrt 19.07, OpenWrt 18.06, OpenWrt 15.05 and LEDE 17.01) are end of life and not supported any more.
CREDITS
Thanks to security researcher Sönke Huster from TU Darmstadt ( shuster@seemoo.tu-darmstadt.de ) and Johannes Berg from Intel for identifying the problems and fixing them in the upstream Linux kernel.
[5,6].
REFERENCES
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41674
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42719
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42720
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42721
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42722
https://lwn.net/ml/oss-security/20221013101046.GB20615@suse.de/
https://lwn.net/ml/oss-security/ff7256bc-418b-e833-18d8-bc9700f6d77e@seemoo.tu-darmstadt.de/

8

[Assistant]
I am using 19.07.10 and my devices cannot be upgraded due to 4/32 issue. What is the worse consequence which I can expect from these vulnerabilities being exploited?

2 Replies
1

None, as the issue arose with later kernel version.

4

Well, as anomeome mentioned, not this issue, but others - some of which might be remotely exploited (if not now, then surely a few months down the line).

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.3 Third service release

Hi,
The OpenWrt community is proud to announce the third service release of OpenWrt 21.02. It fixes security issues, improves device support, and brings a few bug fixes.
We recently moved our bugs to GitHub, please report issues over there (after checking that nobody else posted the same issue before).
https://github.com/openwrt/openwrt/issues/
Download firmware images via the Firmware Selector or directly from our download servers:
• https://firmware-selector.openwrt.org
• https://downloads.openwrt.org/releases/21.02.3/
Main changes from OpenWrt 21.02.2:
Security fixes
wolfssl: Fix multiple security problems (CVE-2022-25638, CVE-2022-25640)
openssl: Fix security problem (CVE-2022-0778)
zlib: Backport security fix for a reproducible crash in compressor
Device support
Support for the following devices was added:
Yuncore XD3200
Yuncore A930
MikroTik RouterBOARD mAPL-2nD (mAP lite)
ramips: Make memory detection more reliable
ramips: Fix reboot for remaining 32 MB boards
x86: Add pata_sis driver
ipTIME mt7620 devices: Fix flash detection
Turris Omnia: Improve detection of u-boot environment with U-boot 2021.09
Ubiquiti UniFi: Fix label MAC address
mvebu: udpu: Fix initramfs booting
a20-olinuxino-lime2: Fix Ethernet link detection on
TP-Link TL-WR1043ND v4: Fix TPLINK_HWREV field
OCEDO Raccoon: Fix link for long cables
Ubiquiti UniFi AP Outdoor+: Fix label MAC address
TP-Link WPA8630Pv2: Move to ath79-tiny target
Improve support for some GPON SFP modules
Various fixes and improvements
Fix SSL certificate validation with some sites especially sites using Let’s Encrypt certificates
hostapd fixes and improvemnts:
fix radius problem due to invalid attributes
Expose more data over ubus
base-files: Call “sync” after initial setup
imagebuilder: Fix broken image generation with external targets
Core components
Update Linux kernel from 5.4.179 to 5.4.188
Update openssl from 1.1.1m to 1.1.1n
Update cypress-firmware from 5.4.18-2020_0402 to 5.4.18-2021_0812
Update mac80211 from 5.10.85 to 5.10.110
Update wolfssl from 5.1.1 to 5.2.0
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.3
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.3#regressions
For a detailed list of all changes since 21.02.2, refer to
https://openwrt.org/releases/21.02/changelog-21.02.3
To download the 21.02.3 images, navigate to:
https://downloads.openwrt.org/releases/21.02.3/
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

29

[Assistant]
Thanks for the release.
Here, stable so far:
Linksys EA8500: main router
BanIP, adblock, dhcp, wireguard + vpn-policy, ntp, Unbound DoT (2nd)
Asus GT-AC5300: Unbound DoT (1st), adblock

2

looks like it sysupgrade.openwrt.org doesn't have this version yet. I noticed where was some delay for them in last version too, how long it takes for them to get newest version?

1

Until the service admin manually adds the new version number, that could be in the next 5 minutes or may take until the ~weekend.

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 22.03.0-rc4 fourth release candidate

Hi,
The OpenWrt community is proud to announce the fourth release candidate of the upcoming OpenWrt 22.03 stable version series. It incorporates over 3500 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-rc4/
OpenWrt 22.03.0-rc2 was skipped because the URL of the release repository was not updated correctly.
OpenWrt 22.03.0-rc3 was skipped because of a severe problem in firewall4.
Changes between OpenWrt 22.03.0-rc1 and 22.03.0-rc4
Software updates
Linux kernel updated to version 5.10.120 (from 5.10.111 in v22.03.0-rc1)
wolfssl Update to version 5.3.0 (from 5.2.0 in v22.03.0-rc1)
openssl Update to version 1.1.1o (from 1.1.1n in v22.03.0-rc1)
Misc changes
ucode: many updates
firewall4: many updates
Multiple fixes for flow offload fixing problems with IPv6 and PPPoE
Device support
New devices
ath79: TP-Link Deco M4R
ath79: Netgear WNDAP360
ath79: MikroTik RouterBOARD 952Ui-5ac2nD (hAP ac lite)
ath79: MikroTik RouterBOARD 951Ui-2nD (hAP)
ath79: Ubiquiti NanoBeam M5
bcm53xx: Asus RT-AC88U
ipq806x: Arris TR4400 v2
ramips: YunCore AX820
ramips: TP-Link RE650 v2
ramips: Wavlink WL-WN533A8
ramips: SERCOMM NA502S
ramips: Cudy X6
realtek: ZyXEL GS1900-16
realtek: ZyXEL GS1900-24E
lantiq: Add upstream vectoring support
Many other changes in all parts of OpenWrt, see Chnagelog for details.
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.0-rc4
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/22.03/notes-22.03.0-rc4#known_issues
For a detailed list of all changes since 22.03-rc1, refer to
https://openwrt.org/releases/22.03/changelog-22.03.0-rc4
To download the 22.03.0-rc4 images, navigate to:
https://downloads.openwrt.org/releases/22.03.0-rc4/
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
21

[Assistant]
Thank you all for yor work, I will test it soon in my zbtlink zbt-we1326 and will report back any issue

Installed in my WAC104 setup as a dumb AP. No issues.

Just sysupgraded a ZyXEL GS1900-24HPv1 from rc3 to rc4 with keeping the config and is still working, even the dualboot to OEM ZyXEL.

2