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

[User]
Title: OpenWrt 21.02.0 second release candidate

Hi,
The OpenWrt community is proud to announce the second release candidate of the upcoming OpenWrt 21.02 stable version series. It incorporates over 5800 commits since branching the previous OpenWrt 19.07 release and has been under development for about one and a half year.
Changes between OpenWrt 21.02.0-rc1 and 21.02.0-rc2
New network configuration syntax
There have been several changes to the network configuration syntax in /etc/config/network:
in config interface, option ifname has been renamed to device (since it refers to a device section)
in config device of type bridge, ifname has been renamed to ports
for new installs, the generated configuration now creates separate sections for layer 2 (config device) and layer 3 (config interface) configuration
The old syntax is still supported to facilitate transition, and there is no automated migration when upgrading.
However, the LuCI web interface detects old-style configuration and will propose to migrate it to the new syntax. This is necessary to be able to edit network configuration through LuCI.
The new configuration style looks like this:
config device
    option name 'br-lan'
    option type 'bridge'
    option macaddr '00:01:02:XX:XX:XX'
    list ports 'lan1'
    list ports 'lan2'
    list ports 'lan3'
    list ports 'lan4'

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

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

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

config interface 'wan6'
    option device 'eth1'
    option proto 'dhcpv6'
This example uses DSA with lanX interface names. A non-DSA device would use more classical ethX interface names.
LuCI update
LuCI has been updated to support the most recent network syntax (and migrate old config files if needed). In some cases migration will take 2 steps.
Support for configuring devices (config device UCI sections) was added. It can be used for setting layer 2 options (like MTU and MAC address). It also supports bridge devices (including VLAN tagging).
LuCI HTTPS
LuCI is now available over HTTPS in addition to HTTP in the default images.
After an upgrade from OpenWrt 19.07 to OpenWrt 21.02 unencrypted HTTP requests are redirected to HTTPS. On fresh OpenWrt 21.02 installations they are not redirected. Deactivate the redirect to HTTPS like this:
uci set uhttpd.main.redirect_https=0
uci commit uhttpd
service uhttpd reload
Software updates
Linux kernel updated to version 5.4.119 (from 5.4.111 in v21.02.0-rc1)
mac80211 updated to version 5.10.34-1 (from 5.10.16-1 in v21.02.0-rc1)
mac80211 backport upstream fixes for the new FragAttacks vulnerabilities in 802.11
mt76 updated to latest version
dnsmasq updated to version 2.85 (from 2.84 in v21.02.0-rc1)
busybox updated to version 1.33.1 (from 1.33.0 in v21.02.0-rc1)
Misc changes
Linux kernel fix parsing fixed subpartitions
Linux kernel Activate FORTIFY_SOURCE for MIPS kernel 5.4
busybox add SRV support to nslookup_lede.c patch
busybox disable PREFER_IPV4_ADDRESS
openwrt-keyring only copy sign key for 21.02
sdk, imagebuilder unset BINARY_FOLDER and DOWNLOAD_FOLDER in final archives
uqmi fix network registration loop
Device support
Lantiq DSL multiple backports for DSL statistics
New devices MikroTik SXTsq 5 ac, MikroTik hAP ac2
Device fixes for ALFA Network devices, Youku YK1, TP-Link AD7200,
TP-Link EAP-225, TP-Link TL-WR810N v1, MikroTik RB922UAGS-5HPaCD
Known issues
LuCI network migration tool doesn't migrate custom bridge MAC addresses. Custom device MAC has to be set again manually.
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/21.02/notes-21.02.0-rc2
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.0-rc2#known_issues
For a detailed list of all changes since 21.02.0-rc1, refer to
https://openwrt.org/releases/21.02/changelog-21.02.0-rc2
To download the 21.02.0-rc2 images, navigate to:
https://downloads.openwrt.org/releases/21.02.0-rc2/
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements: https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum: https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at https://openwrt.org/contact
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Have fun!
The OpenWrt Community

1 Reply
26

[Assistant]
Can I install certbot and install letsencrypt certificates?

1 Reply

Upgraded wndr3700v2
No issues
Luci migration of network config also no issues.

1

Thanks to all the OpenWrt developers.
No issues encountered so far with D-Link DIR-882.


[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.5 fifth 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.5
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/22.03.5/targets/
Main changes between OpenWrt 22.03.4 and OpenWrt 22.03.5:
Security fixes
CVE-2023-0464: openssl: Excessive Resource Usage Verifying X.509 Policy Constraints
CVE-2023-0465: openssl: Invalid certificate policies in leaf certificates are silently ignored
Device support
Archer AX23 / MR70X: Reduce SPI-frequency
Aruba AP-105: Create APBoot compatible image
Buffalo WSR-600DHP: Fix boot loop
Various fixes and improvements
Fix UBI (Unsorted Block Images) bug which prevented some devices from booting
Fix ccache compile with GCC 13
Core components update
Update uclient from 2021-05-14 to 2023-04-13
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.5
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/22.03/notes-22.03.5#known_issues
For a detailed list of all changes since 22.03.4, refer to
https://openwrt.org/releases/22.03/changelog-22.03.5
To download the 22.03.5 images, navigate to:
https://downloads.openwrt.org/releases/22.03.5/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=22.03.5
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
Have fun!
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact

23

[Assistant]
We need to wait for the asu server's builds to catch up...

1

Thanks devs!
Quick note, Netgear R7800 and Buffalo WZR-HP-AG300H sysupgraded (keeping config) from 22.03.4 using local imagebuilder, no regressions. Units' configuration described here.

Upgraded to 22.03.5 on xiaomi 4a gig v1 and successful.

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: OpenWrt 22.03.0-rc5 fifth release candidate

Hi,
The OpenWrt community is proud to announce the fifth 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 using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=22.03.0-rc5
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/22.03.0-rc5/
Changes between OpenWrt 22.03.0-rc4 and 22.03.0-rc5
Software updates
Linux kernel updated to version 5.10.127 (from 5.10.120 in v22.03.0-rc4)
openssl update to version 1.1.1p (from 1.1.1o in v22.03.0-rc4)
mt76 update to version 2022-07-03 (from 2022-03-15 in v22.03.0-rc4)
wireless-regdb update to version 2022.06.06 (from 2022.02.18 in v22.03.0-rc4)
Misc changes
firewall4: multiple updates
iptables: default to ip(6)tables-nft
hostapd: Add owe_transition_ifname option
Device support
New devices
ath79: RouterBOARD mAP
mediatek: Ubiquiti UniFi 6 LR v2
rampis: ZyXEL NBG-419N v2: fix booting
Activate ARM64 crypto extensions in supported ARM64 target kernels
Update uboot-mvebu to version v2022.04
ipq40xx: mikrotik: provide BDF-s on demand
Many other changes in all parts of OpenWrt, see Changelog for details.
https://openwrt.org/releases/22.03/changelog-22.03.0-rc5
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.0-rc5
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/22.03/notes-22.03.0-rc5#known_issues
For a detailed list of all changes since 22.03-rc4, refer to
https://openwrt.org/releases/22.03/changelog-22.03.0-rc5
To download the 22.03.0-rc5 images, navigate to:
https://downloads.openwrt.org/releases/22.03.0-rc5/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=22.03.0-rc5
As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.
Have fun!
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at https://openwrt.org/contact

13

[Assistant]
Great news!
Is there an expected lag before the Firmware Selector custom packager recognizes the new RC?

2 Replies

Thank you devs.
Updated:
Belkin RT3200 (UBI) (mediatek/mt7622) at 3 locations.
Netgear R7800 (ipq806x/generic) at 1 location.
TP-Link Archer A7 v5 (ath79/generic) at 2 locations.

1

Updated from rc4 to rc5(x86-64) and ipv6 broke.
Router gets an ipv6 address on wan, but no traffic passes. Clients don't even get an address.
Haven't done any further troubleshooting yet.
EDIT: router actually has ipv6 connectivity, dns was being weird. Still nothing on clients though.
Removed all the *tables-legacy packages and no change.
EDIT2: ipv6 eventually started working, so I put all my packages back the way things started, and ipv6 kept working. Guess it was just a coincidental ISP outage.


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

Hi,
The OpenWrt community is proud to announce the eighth 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.7 are:
Security fixes
Fix FragAttacks (fragmentation and aggregation attacks) vulnerabilities in cfg80211, mac80211, ath10k and ath10k-ct
We are not sure if some closed source firmware files are still affected by these problems.
Security Advisory 2021-08-01-1 - XSS via missing input validation of host names displayed (CVE-2021-32019)
Security Advisory 2021-08-01-2 - Stored XSS in hostname UCI variable (CVE-2021-33425)
Security Advisory 2021-08-01-3 - luci-app-ddns: Multiple authenticated RCEs (CVE-2021-28961)
Various security fixes in packages
Major bug fixes
Minor bugfixes to support GCC 11 as host compiler
Device support
TP-Link C7v5 allow flashing from vendor firmware bigger than v1.1
FRIZZ!Box 7320 Activate power supply to USB ports.
Various fixes and improvements
Only pack the signing keys for OpenWrt 19.07 and 21.02 and not the personal keys any more.
Core components
Update Linux kernel from 4.14.221 to 4.14.241
Update mac80211 from 4.19.161-1 to 4.19.193-1
Update ath10k-ct 4.19 driver from 2019-09-09 to 2021-06-03
Update OpenVPN from 2.4.7 to 2.4.11
Update openssl from 1.1.1i to 1.1.1k
Update mbedtls from 2.16.9 to 2.16.10
Update wolfssl from 4.6.0 to 4.7.0
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/19.07/notes-19.07.8
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/19.07/notes-19.07.8#regressions
For a very detailed list of all changes since 19.07.7, refer to
https://openwrt.org/releases/19.07/changelog-19.07.8
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.8 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.8/targets/
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
23

[Assistant]
Thank you for reducing e-waste by keeping our legacy devices alive using this version!
Note that RSS feeds are already available, we have them hooked up in the Matrix room as well:
https://forum.openwrt.org/c/announcements/14.rss
https://openwrt.org/feed.php?type=rss&mode=list&sort=date&ns=advisory&linkto=current&content=html
https://github.com/openwrt.atom
https://github.com/openwrt/openwrt/releases.atom

1 Reply
1

FYI
ar71xx NAND devices not there
https://downloads.openwrt.org/releases/19.07.7/targets/ar71xx/nand/
https://downloads.openwrt.org/releases/19.07.8/targets/ar71xx/

1 Reply

This is a service release to fix security in the old stuff. If you want a new release with features like DSA you should try a 21 release candidate

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 One - celebrating 20 years of OpenWrt

@blogic
posted following on the OpenWrt mailing list for developers:
tl;dr
In 2024 the OpenWrt project turns 20 years! Let's celebrate this anniversary by launching our own first and fully upstream supported hardware design.
If the community likes the idea outlined below in greater details, we would like to start formal vote.
The idea
It is not new. We first spoke about this during the OpenWrt Summits in 2017 and also 2018. It became clear start of December 2023 while tinkering with Banana Pi style devices that they are already pretty close to what we wanted to achieve in ’17/‘18. Banana PIs have grown in popularity within the community.
They boot using a self compiled Trusted Firmware-A (TF-A)and upstream U-Boot (thx MTK/Daniel) and some of the boards are already fully supported by the upstream Linux kernel. The only non open source components are the 2.5 GbE PHY and Wi-Fi firmware blobs running on separate cores that are independent of the main SoC running Linux and the DRAM calibration routines which are executed early during boot.
I contacted three project members (pepe2k, dangole, nbd) on December 6th to outline the overall idea. We went over several design proposals, at the beginning we focused on the most powerful (and expensive) configurations possible but finally ended up with something rather simple and above
all,feasible. We would like to propose the following as our "first" community driven HW platform called "OpenWrt One/AP-24.XY".
Together with pepe2k (thx a lot) I discussed this for many hours and we worked out the following project proposal. Instead of going insane with specifications, we decided to include some nice features we believe all OpenWrt supported platforms should have (e.g. being almost unbrickable with multiple recovery options, hassle-free system console access, on-board RTC with battery backup etc.).
This is our first design, so let's KiSS!
Hardware specifications:
SOC: MediaTek MT7981B
Wi-Fi: MediaTek MT7976C (2x2 2.4 GHz + 3x3/2x2 + zero-wait DFS 5Ghz)
DRAM: 1 GiB DDR4
Flash: 128 MiB SPI NAND+ 4 MiB SPI NOR
Ethernet: 2x RJ45 (2.5 GbE + 1 GbE)
USB (host): USB 2.0 (Type-A port)
USB (device, console): Holtek HT42B534-2 UART to USB (USB-C port)
Storage: M.2 2042 for NVMe SSD (PCIe gen 2 x1)
Buttons: 2x (reset + user)
Mechanical switch: 1x for boot selection (recovery, regular)
LEDs: 2x (PWM driven), 2x ETH Led (GPIO driven)
External hardware watchdog: EM Microelectronic EM6324 (GPIO driven)
RTC: NXP PCF8563TS (I2C) with battery backup holder(CR1220)
Power: USB-PD 12-25V on USB-C port (optional 802.3at/af PoE via RT5400 module)
Expansion slots: mikroBUS
Certification: FCC/EC/RoHS compliance
Case: PCB size is compatible to BPi-R4 and the case design can be re-used
JTAG for main SOC: 10-pin 1.27 mm pitch (ARM JTAG/SWD)
Antenna connectors: 3x MMCX for easy usage, assembly and durability
Schematics: these will be publicly available (license TBD)
GPL compliance: 3b. "Accompany it with a written offer ... to give any third
party ... a complete machine-readable copy of the corresponding source code"
Price: aiming for below 100$
How will the device be distributed?
OpenWrt itself cannot handle this for a ton of reasons. This is why we spoke with the SFC early. The idea is that BPi will distribute the device using the already established channels and for every device sold a donation will be made to our SFC earmarked fund for OpenWrt. This money can then be used to cover hosting expenses or maybe an OpenWrt summit.
SFC is committed to working with us in various ways on this project —including making sure OpenWrt's trademark is properly respected, that this router is a beautiful example of excellent GPL/LGPL compliance, and that this becomes a great promotional opportunity for our project and FOSS generally!
FAQ
Why are there are 2 different flash chips?
The idea is to make the device (almost!) unbrickable and very easy to recover.
NAND will hold the main loader (U-Boot) and the Linux image and will be the
default boot device
NOR will be write-protected by default (with WP jumper available on the board) and will hold a recovery bootloader (and other essential data, like Wi-Fi calibration)
a dedicated boot select switch will allow changing between NOR and NAND
What will the M.2 slot be used for?
We will use M.2 with M-key for NVMe storage. There is a work-in-progress patch to make PCIe work inside the U-Boot bootloader. This will allow booting other Linux distributions such as Debian and Alpine directly from NVMe.
Why is there no USB 3.x host port on the device?
The USB 3.x and PCIe buses are shared in the selected SoC silicon, hence
only a single High-Speed USB port is available
What is the purpose of the console USB-C port?
Holtek UART to USB bridge with CDC-ACM support on USB-C makes the device ultra easy to communicate with. No extra hardware or drivers will be required. Android for example has CDC-ACM support enabled by default.
What MAC OUI will the device have?
We plan to register an OUI block for OpenWrt which can also be used for
other vendor extensions such as Wi-Fi beacon IEs.
What is the purpose of the mikroBUS connector?
mikroBUS was chosen as we wanted to make the hardware extendable. There are dedicated pins for UART, SPI, I2C buses and RST/INT signals. The standard uses regular 2.54 mm pitch connectors (you can use available mikroBUS modules or just connect to it something else, with 2.54 mm jumper cables).
Why have the RTC on board instead of a mikroBUS module?
We believe there are many things a Wi-Fi (or networking in general) device should have on-board by default. Always having a correct time on the device is crucial in many applications, like VPN, DNSSEC, …
Timeline of events leading up to this e-mail
Forgive us for the lack of public communication during the initial phase(which as you can see was short and quick). We wanted to ensure that this project is feasible before disclosing it to the community. It would be a real shame if we announced something that we later found out to not be feasible thus failing expectations raised within the community.
03.12 - initial idea
06.12 - ping pepe2k, dangole, nbd
07.12 - ping MediaTek and ask if this sounds doable
08.12 - ping jow, Hauke
08.12 - request for call with SFC, we want them involved as soon as possible
09.12 - MediaTek replies and says they can help
09.12 - ping apacar, ynezz, dwmm2, lynxis, rsalvaterra
12.12 - MediaTek spoke with Banana Pi, they also like the idea
18.12 - call with SFC (Hauke joined, we found no prior slot to talk)
20.12 - started writing the U-Boot PCIe driver, made recovery from USB and
android fastboot recovery work.
... and then the end of year celebrations started and not much happened for 2
weeks.
03.01-08.01 - write this text
Thanks,
Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
Signed-off-by: Bradley M. Kuhn <bkuhn@sfconservancy.org>
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Signed-off-by: David Bauer <mail@david-bauer.net>
Signed-off-by: Denver Gingerich <denver@sfconservancy.org>
Signed-off-by: Felix Fietkau <nbd@nbd.name>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: John Crispin <john@phrozen.org>
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Signed-off-by: Paul Spooren <mail@aparcar.org>
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Signed-off-by: Steven Liu <steven.liu@mediatek.com>

6 Replies
133

[Assistant]
I have already donated to OpenWrt several times. I would also like to buy hardware.
However, I have made the experience with SBCs that they are difficult with average knowledge. Almost everything except Raspberry PI is too complicated for me / I ordered some from China and had bad experiences. They are in my cellar.

5

Nice! I hope it happens and it will be a great success so we can see a follow-up with WiFi 6E

3

Amazing idea and it's something I always hoped for. I understand you are looking for a low price point, but not having USB 3.0 is a strange omission even though they do create a bit of noise. I'm so used to sharing files with Samba I wouldn't want to not have it. Also only 128MB flash is odd. Would it even cost more than $1 extra to do 256MB and support advanced-reboot package for a dual-boot firmware? Or even a 4GB eMMC opening up options for Docker? M.2 slot is very cool but this is a performant SoC will be untilized with those specs, it'll handle gigabit no problem with HFO supported meditatek of course. Here is to hoping this is a sucess and you build a more mid range model at more of the $150 price point with those items and a faster SoC.

4


[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-rc6 sixth release candidate

Hi,
The OpenWrt community is proud to announce the sixth 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 using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=22.03.0-rc6
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/22.03.0-rc6/
Changes between OpenWrt 22.03.0-rc5 and 22.03.0-rc6
Software updates
Linux kernel updated to version 5.10.134 (from 5.10.127 in v22.03.0-rc5)
mac80211 updated to version 5.15.58-1 (from 5.15.33-1 in v22.03.0-rc5)
wolfssl updated to version 5.4.0 (from 5.3.0 in v22.03.0-rc5)
openssl update to version 1.1.1q (from 1.1.1p in v22.03.0-rc5)
intel-microcode update to version 20220510 (from 20220207 in v22.03.0-rc5)
Misc changes
wolfssl: Deactivate CPU acceleration by default
wolfssl: Make package shared again
Device support
New devices
ramips: Netgear WAX202
bcm53xx: NAT performance increase
Many other changes in all parts of OpenWrt, see Changelog for details.
https://openwrt.org/releases/22.03/changelog-22.03.0-rc6
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.0-rc6
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/22.03/notes-22.03.0-rc6#known_issues
For a detailed list of all changes since 22.03-rc5, refer to
https://openwrt.org/releases/22.03/changelog-22.03.0-rc6
To download the 22.03.0-rc6 images, navigate to:
https://downloads.openwrt.org/releases/22.03.0-rc6/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=22.03.0-rc6
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]
Not that I mind. But rc6. Have there been as many release candidates for an Openwrt release before?

2 Replies
1

Installed and working fine on a Wavlink Quantum Dax

Installed and working fine on a TP-Link Archer C60 v3.


[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-rc6 - Sixth Release Candidate

Hi,
The OpenWrt community is proud to announce the sixth release candidate of the upcoming OpenWrt 24.10 stable series.
OpenWrt 24.10.0-rc6 incorporates over 5300 commits since branching the previous OpenWrt 23.05 release and has been under development for over one year.
This is just a release candidate and not the final release yet.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org?version=24.10.0-rc6
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/24.10.0-rc6/targets/
Please test this version
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker. https://github.com/openwrt/openwrt/issues
If there is already an existing ticket feel free to comment that the problem also occurs with OpenWrt 24.10.0-rc6.
Changes between OpenWrt 24.10.0-rc5 and 24.10.0-rc6
Target changes:
airoha: Multiple fixes
apm821xx: WNDAP620 + WNDAP660: Fix sysupgrade failures
armsr: change image names to 'combined-efi'
ath79: AR9344: fixes spurious reset hangs
ath79: meraki-mr18: fix initramfs build
ath79: teltonika-rut230: fix failsafe boot without SIM tray
ath79: zte-mf28x-common: fix initramfs execution
d1: Use correct module for devices with wifi
ipq4019: FritzBox 7530: Fix initialization of Lantiq DSL
ipq40xx: Fix MAC address
kernel: Realtek PHY improvements
lantiq: AVM FritzBox 7430: Add fritz_cal_extract with reverse option
lantiq: xrx200_legacy: disable unused PHY drivers to reduce image size
mediatek: Xiaomi AX3000t: fix soft brick for the rd23 model
mvebu: WD Cloud Mirror Gen2: Add new device
qualcommax: dl-wrx36: Fix 2.5G port LED-s
ramips: mt7621: Confiabits MT7621 v1: Add new device
ramips: mtk_eth_soc: reduce driver memory usage
realtek: Zyxel GS1900: debounce reset key
rockchip: disable kernel preemption to increase VPN performance
Generic changes:
Linux Kernel update to version 6.6.73
mt76: update to Git HEAD (2025-01-14)
lldpd: bump version to 1.0.18
lldpd: fix config for build without LLDP-MED
hostapd: backport upstream patch to fix setting BSS color
hostapd: fix processing mbssid config option
netifd: improve packet steering on ipq40xx (and possibly others)
wifi-scripts: add macaddr_base wifi-device option
wifi-scripts: add option to set per-device ifname prefix
wifi-scripts: allow per-IF mesh basic rate selection
For a detailed list of changes since OpenWrt 24.10.0-rc6 see the 24.10.0-rc6 changelog.
Highlights in OpenWrt 24.10:
General changes
TLS 1.3 support in default images
mbedtls was updated to version 3.6 which includes support for TLS 1.3
Activate POSIX Access Control Lists and file system security attributes for all file systems on devices with big flash sizes. This is needed by docker nowadays.
This is activated for all targets which do not have the small_flash feature flag. small_flash is set for the ath79/tiny, bcm47xx/legacy, lantiq/ase, lantiq/xrx200_legacy, lantiq/xway_legacy, ramips/mt76x8, ramips/rt288x, ramips/rt305x and ramips/rt3883 targets.
Activate kernel support for Multipath TCP on devices with big flash sizes.
Improved support for WiFi6 (802.11ax) and initial support for WiFi7 (802.11be)
Not many Wifi7 devices are supported by OpenWrt yet
Improved Link Layer Discovery Protocol (LLDP) support
OpenWrt 24.10 uses OPKG only, APK packages are not supported. Only main branch was changed to APK.
Many new devices added
OpenWrt 24.10 supports over 1950 devices. Support for over 100 new devices was added in addition to the device support by OpenWrt 23.05.
Added support for OpenWrt One
Target changes
Added d1 target for AllWinner D1 RISC-V SoC
Added ixp4xx target for Intel XScale IXP4xx SoCs.
Added loongarch64 target for SoCs with Loongson LoongArch CPUs.
Added starfive target for StarFive JH71x0 (7100/7110) SoCs.
Added stm32 target for STMicroelectronics STM32 SoCs.
Renamed ipq807x target to qualcommax.
Removed ath25 target. It supported Atheros ieee80211g devices with maximum 16MB RAM
Removed bcm63xx target. It supported some Broadcom DSL MIPS SoCs and was replaced by the bmips target. The Broadcom DSL itself was never supported.
Removed octeontx target. It supported the Octeon-TX CN80XX/CN81XX based boards
Removed oxnas target. It supported the PLXTECH/Oxford NAS782x/OX8xx
The qoriq target for the NXP QorIQ (PowerPC) SoCs is built
The ipq806x target for Qualcomm Atheros IPQ806X SoCs was converted to DSA
Added support for Airoha AN8855 DSA Switch (Xiaomi AX3000T ship both Mediatek and Airoha Switch in the same revision)
Core components update
Core components have the following versions in 24.10.0-rc6:
Updated toolchain:
musl libc 1.2.5
glibc 2.38
gcc 13.3.0
binutils 2.42
Updated Linux kernel
6.6.73 for all targets
Network:
hostapd master snapshot from September 2024, dnsmasq 2.90, dropbear 2024.86
cfg80211/mac80211 from kernel 6.12.6
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs handling for Airoha AN8855 is currently not supported. Xiaomi AX3000T with Airoha Switch mounted will have Switch LEDs powered OFF. (problem will be addressed in later OpenWrt SNAPSHOT and later Openwrt 24.10 minor release)
5GHz Wifi on TP-Link Archer C60 v1, TP-Link Archer C6 v2 and probably more devices with ath10k Wifi chip does not work, see https://github.com/openwrt/openwrt/issues/14541
Ethernet link unstable on some mt7530 switches. Deactivate EEE (Energy-Efficient Ethernet) as a workaround, see: https://github.com/openwrt/openwrt/issues/17351
2.5G PHY on Netgear WAX206, Cudy TR3000 and Ruijie RG-X60 Pro broken, see https://github.com/openwrt/openwrt/issues/17183
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.0-rc6
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.0-rc6#known_issues
For a detailed list of all changes since 24.10.0-rc5, refer to
https://openwrt.org/releases/24.10/changelog-24.10.0-rc6
To download the 24.10.0-rc6 images, navigate to:
https://downloads.openwrt.org/releases/24.10.0-rc6/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=24.10.0-rc6
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

21

[Assistant]
A few issues with upgrades you may run into:
It looks like at least x86 and ath79 haven't been picked up by ASU server, so Firmware Selector, owut and LuCI app are failing to build those targets (error is Unsupported profile: ...). Reported to aparcar.
The LuCI Attended Sysupgrade app has a bug, so it's not picking up the latest 24.10 rc. PR submitted an hour ago. LuCI app users will need to either use Firmware Selector or owut until the package gets updated.

4 Replies
8

Flashed on my GL-MT6000. Lots of added packages etc, fantastic so far.
A few comments prior to final release:
daemon.err hostapd: nl80211: kernel reports: integer out of range - log spam is fixed! I see 7673390 . Thanks, wifi is working awesome in general too.
Packet Steering: Enabled (All CPUs) option 2 is gone from LuCI from rc5 to rc6. Only Enabled or Disabled are available now. Performance with enabled seems good, but anyone know if this was intentional? Might have been prior to d889c27. Coded as: o.value('2',_('Enabled (all CPUs)')); does not show up.
Rockchip: please backport 17683 to 24.10. NanoPi targets really need the affinity tuning for better performance due to hybrid cores.
Ksmbd: Please backport 225519 to 24.10. Better config settings for better ksmbd performance.
Thanks to all the devs!

3 Replies
5

I see a lot of hostapd logentries on my GL-MT6000 on both RC5 and RC6. It seems to happen when devices roam from 2.4 to 5GHz bands. Initial wireless connection is slow to establish, but once connected there are no issues.
This is from an iPhone:
Thu Jan 23 01:28:10 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:28:10 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:28:18 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
Thu Jan 23 01:30:01 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:32:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:32:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:32:19 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:32:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:32:19 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:32:19 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:32:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Thu Jan 23 01:32:20 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 01:34:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:34:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:34:19 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:34:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:34:19 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:34:19 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:34:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Thu Jan 23 01:34:20 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 01:36:00 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:00 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:00 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:00 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:00 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:00 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:00 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Thu Jan 23 01:36:01 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 01:36:02 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:02 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:02 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:02 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:02 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:07 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:07 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:07 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:07 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:15 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:15 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:15 2025 daemon.notice hostapd: phy1-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:15 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:15 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:15 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:23 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:23 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:23 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:23 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:30 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:30 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:30 2025 daemon.notice hostapd: phy1-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:30 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:30 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:30 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:38 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:38 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:38 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:38 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:45 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:45 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:45 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:45 2025 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:45 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:45 2025 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:37:15 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
And an Intel AC adapter:
Thu Jan 23 12:11:17 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:11:17 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 2)
Thu Jan 23 12:11:17 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 12:11:17 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 12:11:17 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:17 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:13:17 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 12:13:17 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:17 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:26 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:13:26 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 12:13:26 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:26 2025 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 12:13:26 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 12:13:26 2025 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:56 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 12:14:23 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:14:23 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 2)
Thu Jan 23 12:14:23 2025 daemon.notice hostapd: phy1-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 12:14:23 2025 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:14:25 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 12:14:25 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 12:14:25 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:14:53 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 12:15:09 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:15:09 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 12:15:09 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 12:15:09 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:15:09 2025 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 12:15:09 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 12:15:09 2025 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:15:39 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
I come from a snapshot image built around May 2024, that did not give any of these entries. For reference my /etc/config/wireless:
config wifi-device 'radio0'
 option type 'mac80211'
 option path 'platform/soc/18000000.wifi'
 option country 'NL'
 option htmode 'HE20'
 option band '2g'
 option channel '1'

config wifi-iface 'wifinet0'
 option device 'radio0'
 option network 'lan'
 option mode 'ap'
 option ssid 'redacted'
 option encryption 'psk2+ccmp'
 option key 'redacted'
 option ieee80211w '1'

config wifi-device 'radio1'
 option type 'mac80211'
 option path 'platform/soc/18000000.wifi+1'
 option country 'NL'
 option htmode 'HE80'
 option band '5g'
 option channel '36'

config wifi-iface 'wifinet1'
 option device 'radio1'
 option network 'lan'
 option mode 'ap'
 option ssid 'redacted'
 option encryption 'psk2+ccmp'
 option key 'redacted'
 option ieee80211w '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 23.05.4 - Service Release

Hi,
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 23.05 stable series. It improves device support and brings a few bug fixes including security fixes.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=23.05.4
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/23.05.4/targets/
Main changes between OpenWrt 23.05.3 and OpenWrt 23.05.4
Device support
Support for the following devices was added:
ath79: Huawei AP5030DN
mediatek: Unielec U7981-01
mediatek: Xiaomi AX3000T
mediatek: Cudy TR3000 v1
mediatek: Zbtlink ZBT-Z8103AX
mediatek: Adtran SmartRG Bonanza Peak series
mediatek: YunCore AX835
mediatek: Comfast CF-E393AX
mediatek: D-Link EAGLE PRO AI R32
mediatek: JDCloud RE-CP-03
mediatek: Netcore N60
mediatek: D-Link AQUILA PRO AI M30
mediatek: Cudy M3000 v1
mpc85xx: Hewlett Packard MSM460
ramips: D-Link DIR-806A B1
ramips: Netgear EAX12 series
ramips: Edimax BR-6208AC V2
ramips: Cudy TR1200 v1
armsr: enable framebuffer emulation for virtio-gpu/drm displays used by Hetzner console
armsr: add Realtek and smsc Ethernet phy drivers to the default image
armsr: Renesas: RZ: Ethernet module and ttySC0
ipq40xx: Linksys WHW03 v2: enable additional 5 GHz channels
ipq40xx: Engenius EAP1300: Enable device
ipq40xx: NETGEAR EX6150v2: fix broken image generation
ipq806x: Meraki MR52: swap LAN LEDs
mediatek: backport multiple Ethernet fixes from master
mediatek: filogic: fix failsafe mode on devices with no lan1
mediatek: Xiaomi WR30U: drop device with NMBM layout
mediatek: Xiaomi WR30U: fix sysupgrade error
mpc85xx: Enterasys WS-AP3710i: fix boot
mpc85xx: Enterasys WS-AP3710i: fix eth mac-address
rockchip: improve stability and fix console
realtek: D-Link DGS-1210-16: Fix reboot hang
realtek: Trap LLDP packets to the CPU and do not forward
ramips: limit max spi clock frequency to 50 MHz
Various fixes and improvements
Added missing and fixed license information for multiple packages
Added CPE IDs to multiple packages
Fix communication with tethered iOS devices in CDC NCM mode
base-files: fix uid/gid auto-enumeration to avoid 16-bit limit
wifi-scripts: fix creation of IBSS in legacy (non-HT) mode
hostapd: don't ignore probe-requests with invalid DSSS params
mac80211: backport many (security) fixes
mac80211: add missing config for third 160MHz width for 5GHz radio
kernel: Add missing dependencies for kmod-fs-btrfs
kernel: allow installing kmod-ipt-tee and kmod-nft-dup-inet at the same time.
config: Enable ext4 journaling by default.
linux-firmware: package Intel AX201 firmware
Core components update
Update Linux from 5.15.150 to 5.15.162
Update mac80211 from 6.1.24 to 6.1.97-1
Update mt76 from 2023-09-11 to 2024-04-03
Update wireless-regdb from 2024.01.23 to 2024.07.04
Update libxml2 from 2.11.4 to 2.12.5
Update mbedtls from 2.28.7 to 2.28.8
Update OpenSSL from 3.0.13 to 3.0.14
Update wolfssl from 5.6.4 to 5.7.2
Update unetd from 2023-05-31 to 2024-03-31
Update ucode from 2023-11-07 to 2024-07-11
Update intel-microcode from 20240312 to 20240531
Upgrading to 23.05.4
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.4 was signed with the wrong signing keys. The keys from OpenWrt snapshot were used for OpenWrt 23.05.4, OpenWrt 23.05.3, OpenWrt 23.05.2, OpenWrt 23.05.0 and the release candidates. A later OpenWrt 23.05 service release will use a different key.
See up to date information here:
https://openwrt.org/releases/23.05/notes-23.05.4#known_issues
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/23.05/notes-23.05.4
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/23.05/notes-23.05.4#known_issues
For a detailed list of all changes since 23.05.3, refer to
https://openwrt.org/releases/23.05/changelog-23.05.4
To download the 23.05.4 images, navigate to:
https://downloads.openwrt.org/releases/23.05.4/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=23.05.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

1 Reply
40

[Assistant]
Thanks for you work hauke and to everyone else that contributed to this release!

1

Upgraded my RT3200 and WDR4300 dumb AP just fine. Everything working as expected.
Thanks devs!

1

TP-LINK Archer C2600 v1 and two Archer A7s updated using Luci from 23.05.3 to 23.05.4 with settings kept, missing packages installed and devices rebooted.
So far all appears to be working normally.
Thanks again to all who do the work to make this not just possible, but easy.

1


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

[User]
Title: OpenWrt 21.02.2 Second service release

Hi,
The OpenWrt community is proud to announce the second 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).
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.2/
Main changes from OpenWrt 21.02.1
Device support
Support for the following devices was added:
Xiaomi AIoT Router AC2350
Linksys EA6300 & EA9200
Netgear RAXE500
TP-Link TL-WA1201 v2
Minew G1-C: Allow dynamic RAM sizes
Fix U-Boot hang on lantiq danube-s v1.5 with MX29LV640EB NOR
TP-Link tl-mr3020-v3: Fix switch topology
Luxul XWR-3150 LAN: Fix ports numbering
WD MyBook Live DUO: Fix USB-Port
Turris Omnia: Use SFP module, if present
OpenMesh OM5P-AC v2: Fixed device tree
Various fixes and improvements
Add new rpcapd package
chmod 1777 /var/lock to follow FHS 3.0 guideline
netifd: fix deletion of ip tunnels (FS#4058)
multiple mac80211 backports:
Add support Wifi 6 GHz band and HE options in scripts
mac80211: fix IBSS/adhoc mode for brcmfmac
Add ath10k smallbuffers
Core components
Update Linux kernel from 5.4.154 to 5.4.179
Update mac80211 from 5.10.68 to 5.10.85
Update wolfssl from 4.8.1 to 5.1.1
Update wireless-regdb from 2021.04.21 to 2021.08.28
Update mt76 from 2021-06-06 to 2021-12-03
Update busybox from 1.33.1 to 1.33.2
Update intel-microcode from 20200616 to 20210608
Update linux-firmware from 20201118 to 20211216
Update openssl from 1.1.1l to 1.1.1m
Update mbedtls from 2.16.11 to 2.16.12
Regressions
Certificate validation fails in wolfssl against some sites especially sites using lets encrypt certificates. This affects for example wget in the default configuration #9283
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.2
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.2#known_issues
For a detailed list of all changes since 21.02.1, refer to
https://openwrt.org/releases/21.02/changelog-21.02.2
To download the 21.02.2 images, navigate to:
https://downloads.openwrt.org/releases/21.02.2/
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.
Sunshine!
The OpenWrt Community

1 Reply
47

[Assistant]
Great work guys, thanks.
I minor remark, the links are not updated in the Table of Hardware: Firmware downloads. At least not for the TP-Link TL-MR3420 V5
I found the 21.02.2 firmware version in here:
https://downloads.openwrt.org/releases/21.02.2/targets/ramips/mt76x8/

2 Replies

Congrats on the big release, some great fixes included here. Sticking with a Master snapshot on my WRT32X for now have 75 day uptime.
Support for the RAXE500
Wait, this is a high end WiFi 6E router, is this a typo?

Excellent news! Upgraded my WRT1900ACS V1 and my WAC104 from 21.02.1. No issues.
Developers: Well done and much appreciation.


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

Hi,
The OpenWrt community is proud to announce the newest service release of OpenWrt 19.07. It fixes security issues, improves device support, and brings a few bug fixes.
OpenWrt 19.07.10 is the final release of the 19.07 release branch, this branch is now end of life and we will not fix problems on this branch any more, not even severe security problems. We encourage all users still using OpenWrt 19.07 to upgrade to OpenWrt 21.02 or more recent OpenWrt versions.
Download firmware images via the Firmware Selector or directly from our download servers:
https://firmware-selector.openwrt.org
https://downloads.openwrt.org/releases/19.07.10/
The main changes from OpenWrt 19.07.9 are:
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
OCEDO Raccoon: Fix link for long cables with
MikroTik wAP: Fix device detection
Various fixes and improvements
imagebuilder: Fix broken image generation with external targets
imagebuilder: Fix partition signature
patchelf: Backport fix for rpath endianness
base-files: Call “sync” after initial setup
ubus: backport Fixes for UAF and other issues
Core components
Update Linux kernel from 4.14.167 to 4.14.275
Update mac80211 from 4.19.221-1 to 4.19.237-1
Update openssl from 1.1.1m to 1.1.1n
Update wolfssl from 4.7.0 to 5.2.0
Regressions
at91 images are not created any more because the build needs Python.h which is not installed on the build bots.
To fix this issue export the missing environmental variable before using the ImageBuilder: export SOURCE_DATE_EPOCH=1
oxnas/ox820 images are not created any more because of a build problem
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/19.07/notes-19.07.10
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/19.07/notes-19.07.10#regressions
For a very detailed list of all changes since 19.07.9, refer to
https://openwrt.org/releases/19.07/changelog-19.07.10
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.10 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.10/targets/
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
5

[Assistant]
Many thanks for this release.
Upgraded Archer A7v5 successfully.

Thanks update/preform reset on my MikroTik
Summary

Sorry, I am curious.
Why people use 19.07.10 instead of 21.02.3?
All my devices run on 21.02.3, I not know the reason why I should use 19.07.10

4 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: The OpenWrt Firmware Selector

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!
firmware-selector.openwrt.org
OpenWrt Firmware Selector

3 Replies
91

[Assistant]
Typed "4300", there are two firmwares for the same model:

One has platform ar71xx/generic, the other has ath79/generic. Is that how it should be, or should only a new platform be recommended? Or at least show a notification that ar71xx is deprecated.

1 Reply
3

edit: 20210101 mwarning has done an outstanding job acknowledging and addressing this feedback... and the issues below have been creatively and reasonably resolved...
several images with no information about where / how they should be used... ( is it ext4, squashfs, initramfs... pick one and try? )
@tmomas
raised these issues but was largely ignored by
@aparcar
as many other people seem to have been...
as it stands for many devices...
bjonglez:
allows to easily find a firmware image
is not almost a reality...

2 Replies
2

C7 also showing ar71 builds.
I agree with
@tmomas
post on the list. While the idea of a firmware selector may seem interesting at first, it actually separates the image from the info. It can be useful provably for regular users who upgrade their systems regularly and know the process already, but then again those people are the least who need things to be made easier for them because they already know their way around the download files!
I think such effort could be (or could have been) best redirected to "modernising" the Wiki. It's a huge amount of work, considering the number and the variety of devices, but a progress in that direction is likely to be more helpful on the long run.

1 Reply
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: OpenWrt 22.03.4 service release

_______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 22.03.4, r20123-38ccc47687
 -----------------------------------------------------
OpenWrt 22.03.4
The OpenWrt community is proud to announce the newest point release of the
OpenWrt 22.03 stable version series. It fixes security issues, improves device
support, and brings a few bug fixes.
Get OpenWrt Firmware at:
https://firmware-selector.openwrt.org
https://downloads.openwrt.org/releases/22.03.4/
https://sysupgrade.openwrt.org
Main changes between OpenWrt 22.03.3 and OpenWrt 22.03.4
Only the main changes are listed below. See changelog-22.03.4 for the full changelog.
Security fixes
CVE-2022-4304
CVE-2022-4450
CVE-2022-47522
CVE-2022-47938
CVE-2022-47939
CVE-2022-47940
CVE-2022-47941
CVE-2022-47942
CVE-2022-47943
CVE-2023-0215
CVE-2023-0286
Added devices
05ec70f kernel: add support for XMC XM25QH64C
0657576 ath79: add LTE led for GL.iNet GL-XE300
788a0cf mpc85xx: add support for Watchguard Firebox T10
3c6692b ramips: add support for TP-Link Archer AX23 v1
f5db04e ramips: add support for Mercusys MR70X
711e45e ramips: add support for D-Link DAP-X1860 A1
Fixed issues
#7757 via 4b7f9e4 lantiq-xrx200: fix wan LED on o2 box 6431
#9491 via fea7478 iproute2: add missing libbpf dependency
#10871 via 3bc6d2a tools/dosfstools: fix PKG_SOURCE
#11701 via 50d707e lantiq: fix lzma-loader for Netgear DGN 3500(B)
Improvements
38ccc47 imagebuilder: allow to specific ROOTFS_PARTSIZE
7531ef7 sdk: expose PATENTED an NLS build options*
Core components update
f61c5cf kernel: bump 5.10 to 5.10.176
863288b mac80211: Update to version 5.15.92-1
7c10b7b CI: build: fix external toolchain use with release tag tests
Upgrading to 22.03.4
Sysupgrade can be used to upgrade a device from OpenWrt 21.02 or 22.03 to
22.03.4 and configuration will be preserved in most cases.
Warning
Sysupgrade from 19.07 to 22.03.x is not supported.
Warning There is no migration path for targets that switched from swconfig
to DSA. In that case,
sysupgrade will refuse to proceed with an appropriate error message: Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed
Known issues
#12232 Linksys MR8300 may break after the update, wait for the next service release!

3 Replies
19

[Assistant]
Hi.
Several ipq40xx devices (MR8300, EA8300, EA6350) don't boot under 22.03.4 due to a kernel regression. Please read this : OpenWrt SNAPSHOT r22302 on MR8300
This may also impact other devices from the same target. Don't upgrade to 22.03.4 until a solution is found.

1 Reply
6

Just updated xiaomi router 4a gigabit V1
Without any error...

2

Linksys MR8300/EA8300 images fail to boot.
Please remove these images so users don't run into problems.
More info here: https://forum.openwrt.org/t/openwrt-snapshot-r22302-on-mr8300/154878
This problem has been known for almost a month.

2 Replies
6


[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: Resolved: OpenWrt Image Builder Errors

2025-Feb-14: The issues with the image builder system should now be resolved. If problems persist with Attended Sysupgrade (ASU), OpenWrt Upgrade Tool (OWUT) or the Firmware Selector custom image tool, please report them in this thread.

7

[Assistant]
2025-Feb-17: Removing this from the forum banner since the problems appear to have been resolved.
If new issues arise, please post in the thread linked above.


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

[User]
Title: OpenWrt 23.05.0-rc2 - Second Release Candidate

Hi,
The OpenWrt community is proud to announce the second release candidate of the upcoming OpenWrt 23.05 stable series.
OpenWrt 23.05.0-rc2 incorporates over 4000 commits since branching the previous OpenWrt 22.03 release and has been under development for over one year.
This is just a release candidate and not the final release yet.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=23.05.0-rc2
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/23.05.0-rc2/targets/
Changes between OpenWrt 23.05.0-rc1 and 23.05.0-rc2
Changes in this release candidate since the previous 23.05.0-rc1 release candidate are:
Device support
New devices
ath79: Aruba AP-115
bmips: Observa VH4032N
bmips: Netgear DGND3700 v1
bmips: Netgear DGND3800B
bmips: Netgear EVG2000
bmips: Comtrend VR-3025un
bmips: Comtrend WAP-5813n
bmips: Comtrend AR-5381u
bmips: Actiontec R1000H
bmips: Sercomm AD1018
bmips: Comtrend VG-8050
bmips: NuCom R5010UNv2
bmips: Arcadyan AR7516
filogic: Netgear WAX220
ipq40xx: Buffalo WTR-M2133HP (converted to DSA)
ipq807x: prpl Foundation Haze board
ramips: mt7621: Zbtlink ZBT-WG1608 (32M)
ramips: Beeline SmartBox TURBO+
rockchip: Orange Pi R1 Plus
rockchip: Orange Pi R1 Plus LTS
Fix lzma-loader for
ramips: ASIARF boards
ramips: TP-Link MR600v2: fix image generation for sysupgrade image
mvebu: Fix random crashes in mvneta
armvirt: Added EFI support and renamed to armsr
Add RISC-V support
Added sifiveu target for HiFive Unleashed and Unmatched boards
Many other changes in all parts of OpenWrt, see Chnagelog for details.
Highlights in OpenWrt 23.05.0:
Many new devices added
OpenWrt 23.05 supports over 1770 devices. Support for over 180 new devices was added in addition to the device support by OpenWrt 22.03.
The ipq807x target for the Qualcomm IPQ807x Wifi 6 SoCs was added
The mediatek/filogic subtarget for the Mediatek Filogic 830 and 630 SoCs was added
The sifiveu target for the HiFive RISC-V Unleashed and Unmatched boards
Highlights of device support
Switched ipq40xx target to DSA
VDSL support on AVM FRITZ!Box 7530
Support for devices with 2.5G PHYs
Netgear WAX206 (MT7622)
Asus (TUF Gaming) AX4200 (MT7986A)
Netgear WAX218 (IPQ8074)
Xiaomi AX9000 (IPQ8074)
Dynalink DL-WRX36 (IPQ8074)
2 Gbps WAN/LAN NAT Routing on ramips MT7621 devices
Improved DSL statistics on ubus and in LuCI
Switch from wolfssl to mbedtls as default
OpenWrt switched the default cryptographic library from wolfssl to mbedtls. This library is used for HTTPS/TLS in the Webserver providing LuCI and for the cryptographic operations in hostapd. mbedtls provides security updates in their LTS branch without changing the application binary interface (ABI) of the library. wolfssl provides a stable ABI only for a very limited subset of functions. mbedtls allows us to update only mbedtls without the need to recompile and upgrade all users of mbedtls.
Core components update
Core components have the following versions in 23.05.0-rc2:
Updated toolchain:
musl libc 1.2.4
glibc 2.37
gcc 12.3.0
binutils 2.40
Updated Linux kernel
5.15.118 for all targets
Network:
hostapd master snapshot from March 2023
dnsmasq 2.89
dropbear 2022.82
cfg80211/mac80211 from kernel 6.1.24
System userland:
busybox 1.36.1
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/23.05/notes-23.05.0-rc2
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/23.05/notes-23.05.0-rc2#known_issues
For a detailed list of all changes since 23.05.0-rc1, refer to
https://openwrt.org/releases/23.05/changelog-23.05.0-rc2
To download the 23.05.0-rc2 images, navigate to:
https://downloads.openwrt.org/releases/23.05.0-rc2/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=23.05.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

17

[Assistant]
Installed on my WRT32X with lots of packages added.
Excellent SQM on my 300/20Mbit cable with +0/+0 results, USB3 drive and Samba 4.18 hitting 120 MB/s maxing out gigabit LAN, simple-adblock on etc. The bridge offload hack removal seems to be working from my testing too. This is a great build for me so far, thanks devs.

3

Are the following service releases update mt76 drivers, usually? If not I would hope we get the latest driver in the release.

1 Reply
1

That exact error (customizing installed packages) also happened early on with rc1. In that instance, it took about 4 days after the official announcement for package customization to start working. That was a day after I tagged
@aparcar
(who manages the configuration of sysupgrade.openwrt.org) in a forum comment about it. I don't know if my post had anything to do with it getting fixed or if it was just a coincidence of timing.

1 Reply
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: OpenWrt 22.03.6 sixth 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.6
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/22.03.6/targets/
OpenWrt 22.03 EOL in April 2024
The OpenWrt 22.03 series will be supported till April 2024 according to the OpenWrt security policy. The last release from the OpenWrt 22.03 series is planned for April 2024, 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.5 and OpenWrt 22.03.6:
Device support
Support for the following devices was added:
ramips: Cudy X6 v2
ramips: Keenetic Lite III rev. A
ramips: SNR-CPE-W4N-MT router
ath79: WLR-7100: fix packetloss
ath79: wpj563: enable 2nd USB controller
ath79: TP-Link Archer C7 v2: increase the rfkill debounce interval
bmips: NETGEAR DGND3700v2: fix boot loop
ipq40xx: switch to performance governor by default
ramips: Cudy X6: fixes / improvements
Various fixes and improvements
build: generate index.json
build: fix generation of large .vdi images
lua: fix integer overflow in LNUM patch
dropbear: add ed25519 for failsafe key
treewide: add PKG_CPE_ID to multiple packages
mac80211: fix not set noscan option for wpa_supplicant
hostapd: fix broke noscan option for mesh
hostapd: permit also channel 7 for 2.5GHz to be set to HT40PLUS
Core components update
Update Linux kernel from 5.10.176 to 5.10.201
Update openssl from 1.1.1t to 1.1.1w
Update wolfssl from 5.5.4 to 5.6.4
Update mbedtls from 2.28.2 to 2.28.5
Update mt76 22.03 from 2022-09-06 to 2023-09-11
Update wireless-regdb from 2023.02.13 to 2023.09.01
Update linux-firmware from 20220411 to 20230804
Update intel-microcode from 20220809 to 20230808
Update ca-certificates from 20211016 to 20230311
Update uhttpd from 2022-10-31 to 2023-06-25
Update urngd from 2020-01-21 to 2023-11-01
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.6
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/22.03/notes-22.03.6#known_issues
For a detailed list of all changes since 22.03.5, refer to
https://openwrt.org/releases/22.03/changelog-22.03.6
To download the 22.03.6 images, navigate to:
https://downloads.openwrt.org/releases/22.03.6/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=22.03.6
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
9

[Assistant]
hauke:
OpenWrt 23.03 EOL in April 2024
Header version should be fixed with OpenWrt 22.03 here and on release page and on GitHub.

1 Reply
4

Thanks for that. Asus RT-N18U works. Hopefully will donate some when I get the chance.

(openwrt.org was down for me yesterday, thats why I ask)
I'm hesitant to upgrade, does the unplanned wiki maintenance from yesterday relate to any of this ?
I did not spot any security fixes in the release notes, can I put this of for a week ?

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 23.05.3 - Service Release

Hi,
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 23.05 stable series. It improves device support and brings a few bug fixes including security fixes.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=23.05.3
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/23.05.3/targets/
Main changes between OpenWrt 23.05.2 and OpenWrt 23.05.3
Security fixes
CVE-2023-36328: dropbear: Integer Overflow vulnerability in mp_grow in libtommath
CVE-2023-48795: dropbear: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted
CVE-2023-50868: dnsmasq: The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack
Device support
Support for the following devices was added:
ath79: UniFi UK-Ultra
mediatek: Acelink EW-7886CAX
mediatek: ASUS RT-AX59U
mediatek: ASUS TUF AX6000
mediatek: Buffalo WSR-3200AX4S
mediatek: Cetron CT3003
mediatek: Confiabits MT7981
mediatek: Cudy RE3000 v1
mediatek: D-Link EAGLE PRO AI M32
mediatek: GL.iNet GL-MT6000
mediatek: JCG Q30 PRO
mediatek: Routerich AX3000
mediatek: TP-Link EAP225v5
mediatek: Ubiquiti UniFi 6 Plus
mediatek: Zbtlink ZBT-Z8102AX
mediatek: ZyXEL EX5700 (Telenor)
ramips: Cudy WR1300 v3
ramips: D-Link COVR-X1860 A1
ramips: Rostelecom RT-FE-1A
ramips: Rostelecom RT-FL-1 (Serсomm RT-FL-1)
ramips: Rostelecom S1010 (Serсomm S1010.RT)
ramips: TP-Link EX220 v1
ramips: YunCore G720
ramips: Z-ROUTER ZR-2660
ath79: Nanostation Loco M5 XW: Fix read only jffs2 partition
ath79: TP-Link TL-WDR3600 and TL-WDR4300: Fix spurious reboot hangs
ath79: ubnt-bullet-m-xw: fix Ethernet PHY traffic
ipq807x: edgecore EAP102: fix lan/wan
kirkwood: Ctera C200 V1: fix ubi part name
lantiq: xway: disable SMP: fix boot on some Danube boards and NAT performance
mediatek: MT7981/MT7986: fix Ethernet rx hang issue
meidatek: Mercusys MR90X v1: fix eeprom loading
mpc85xx: Extreme Networks WS-AP3825i: increase available RAM
mvebu: IEI-World Puzzle M90x: fix RTC
ramips: improve mtk_eth_soc resets
ramips: rt305x: Use default uart in lzma-loader
ramips: Sercomm NA502: Fix bootup problem
ramips: Unielec u7621-01: Correct the PCIe port number
realtek: d-link dgs-1210-10p: improve sfp support
realtek: Netgear GS110TPP: fix OEM install
rockchip: Orange Pi R1 Plus LTS: improve Ethernet stability
Various fixes and improvements
mt76: Add mt7922 firmware
mwlwifi: Add support for WPA3
dropbear: Increase scp transfer speed
kernel: fix bridge proxyarp issue with some broken DHCP clients
mac80211: fix min_tx_power setting
kernel: add Aquantia PHY firmware loader patches
hostapd: fix FILS AKM selection with EAP-192
hostapd: fix 11r defaults when using SAE
hostapd: fix 11r defaults when using WPA
hostapd: ACS: Fix typo in bw_40 frequency array on channel 118
Core components update
Update Linux from 5.15.137 to 5.15.150
Update mwlwifi from 2023-04-29 to 2023-11-20
Update mt76 from 2023-08-14 to 2023-09-11
Update netifd from 2023-11-10 to 2024-01-04
Update jsonfilter from 2018-02-04 to 2024-01-23
Update bcm27xx-gpu-fw from 2022-05-16 to 2024-01-11
Update mbedtls from 2.28.5 to 2.28.7
Update openssl from 3.0.12 to 3.0.13
Update wireless-regdb from 2023.09.01 to 2024.01.23
Update intel-microcode from 20230808 to 20240312
Update dnsmasq from 2.89 to 2.90
Upgrading to 23.05.3
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.3 was signed with the wrong signing keys. The keys from OpenWrt snapshot were used for OpenWrt 23.05.3, OpenWrt 23.05.2, OpenWrt 23.05.0 and the release candidates. A later OpenWrt 23.05 service release will use a different key.
See up to date information here:
https://openwrt.org/releases/23.05/notes-23.05.3#known_issues
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/23.05/notes-23.05.3
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/23.05/notes-23.05.3#known_issues
For a detailed list of all changes since 23.05.2, refer to
https://openwrt.org/releases/23.05/changelog-23.05.3
To download the 23.05.3 images, navigate to:
https://downloads.openwrt.org/releases/23.05.3/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=23.05.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

3 Replies
45

[Assistant]
Is it safe to download and install now? Wrt3200acm

2 Replies

Linksys E8450 (UBI): sysupgrade to 23.05.3 successful. Thank you all who contributed to this release.

4

hauke:
OpenWrt 23.05.3 was signed with the wrong signing keys. The keys from OpenWrt snapshot were used for OpenWrt 23.05.3, OpenWrt 23.05.2, OpenWrt 23.05.0 and the release candidates. A later OpenWrt 23.05 service release will use a different key.
Is there anyone looking at updating the release process/workflow to get this right? Or is there a reason to keep using the same key?

1 Reply
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.2 second 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.2
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/22.03.2/targets/
Main changes between OpenWrt 22.03.1 and OpenWrt 22.03.2:
Security fixes
mac80211/cfg80211: Security fixes for BSSID parsing (CVE-2022-41674, CVE-2022-42719, CVE-2022-42720, CVE-2022-42721 and CVE-2022-42722)
See Security Advisory 2022-10-17-1
Device support
Support for the following devices was added:
ZyXEL NWA50AX / NWA55AXE (ramips)
ramips/mediatek: backport NAND flash driver from master
mpc85xx: p1010: make TP-Link WDR4900 v1 build again
Various fixes and improvements
busybox: nslookup: Fix wrongly dropped DNS response on some platforms
Core components update
Update rpcd from 2022-08-24 to 2022-09-21
Update ucode from 2022-08-29 to 2022-10-07
Update firewall4 from 2022-09-01 to 2022-10-14
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.2
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/22.03/notes-22.03.2#known_issues
For a detailed list of all changes since 22.03.1, refer to
https://openwrt.org/releases/22.03/changelog-22.03.2
To download the 22.03.2 images, navigate to:
https://downloads.openwrt.org/releases/22.03.2/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=22.03.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

1 Reply
23

[Assistant]
The release is still not available on https://sysupgrade.openwrt.org/

Working well on GL.iNet GL-B1300, Netgear R6100 and TPlink archer C7v5.
Thanks to the devs!

Installed 22.03.2 on my WRT32X along with lots of added packages: SQM, Adblock, Samba, USB3 storage, Advanced-reboot, etc. Running great. Thanks devs.

4


[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 2020-12-09-1 - SAD DNS - Linux kernel - ICMP rate limiting can be used to facilitate DNS poisoning attack (CVE-2020-25705)

A flaw has been found in the Linux kernel that can make it easier to perform DNS cache poisoning attacks.
OpenWrt is affected in its default configuration, although it is not trivial to actually exploit. The new releases OpenWrt 18.06.9 and OpenWrt 19.07.5 fix the issue: upgrading is highly recommended.
It you cannot upgrade, there is a mitigation: in the firewall configuration, change the input policy of the WAN firewall zone from REJECT to DROP and reload the firewall configuration. This will prevent sending ICMP errors to hosts on the Internet and suppress the attack vector. Note: you don't need to do this if you have already upgraded to a fixed version of OpenWrt.
Full advisory: https://openwrt.org/advisory/2020-12-09-1

1 Reply
7

[Assistant]
bjonglez:
change the input policy of the WAN firewall zone from REJECT to DROP
Isn't this what Steve Gibson has recommended for years? Don't let attackers know you exist by rejecting, simply drop?

1

There are arguments for and against that. See: http://www.chiark.greenend.org.uk/~peterb/network/drop-vs-reject

1 Reply
2

This issue is just one of many related to unencrypted DNS traffic.
To solve the root cause requires to enable DNS encryption:
https://openwrt.org/docs/guide-user/services/dns/start#encryption

1 Reply
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: OpenWrt 21.02.7 seventh 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 and brings a bug fix.
Download firmware images using the OpenWrt Firmware Selector:
https://firmware-selector.openwrt.org/?version=21.02.7
Download firmware images directly from our download servers:
https://downloads.openwrt.org/releases/21.02.7/targets/
The OpenWrt 21.02 stable series is now end of life following the OpenWrt Security support guidelines. We encourage all users of the OpenWrt 21.02 stable series to upgrade to OpenWrt 22.03. We will not fix any security problems, even severe ones in the OpenWrt 21.02 release branch any more.
https://openwrt.org/docs/guide-developer/security#support_status
Main changes between OpenWrt 21.02.6 and OpenWrt 21.02.7:
Security fixes
CVE-2023-0464: openssl: Excessive Resource Usage Verifying X.509 Policy Constraints
CVE-2023-0465: openssl: Invalid certificate policies in leaf certificates are silently ignored
Device support
None
Various fixes and improvements
Fix UBI (Unsorted Block Images) bug which prevented some devices from booting
Core components
Update uclient from 2021-05-14 to 2023-04-13
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/21.02/notes-21.02.7
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/21.02/notes-21.02.7#known_issues
For a detailed list of all changes since 21.02.6, refer to
https://openwrt.org/releases/21.02/changelog-21.02.7
To download the 21.02.7 images, navigate to:
https://downloads.openwrt.org/releases/21.02.7/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=21.02.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

1 Reply
5

[Assistant]
No issues upgrading on WRT1900ACS here either.
Any timetable on v23 release? I'm assuming WRT1900ACS will be supported again with v23.

1

Any news on OpenWrt 23?
Installing and Using OpenWrt
Is it coming 2023-04 or later in summer?

1

This sounds encouraging https://github.com/openwrt/openwrt/issues/10672#issuecomment-1304812810


[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: Security Advisory 2021-02-02-2 - wolfSSL heap buffer overflow in RsaPad_PSS (CVE-2020-36177)

[Assistant]
It's still work in progress, there is not that much information about it available yet (even wolfSSL itself is blank), but according to the very high CVSS score of 9.8 (10 is most severe) it's likely, that this issue has RCE potential.
In wolfSSL prior to version 4.6.0 there exists serious security issue. This wolfSSL library is provided as libwolfssl24 package in OpenWrt and shipped by default in snapshots since August 27th 2020. It's NOT shipped by default in latest stable OpenWrt release 19.07.
Full advisory can be found on dedicated wiki page.
Package upgrade to fixed libwolfssl24 version 4.6.0
You need to update the affected libwolfssl24 package you're using with the command below.
opkg update; opkg upgrade libwolfssl24
Then verify, that you're running fixed version.
opkg list-installed libwolfssl24
The above command should output following for stable OpenWrt 19.07 release and snapshot builds:
libwolfssl24 - 4.6.0-stable-1

11