OpenWrt 23.05.0-rc4 - Fourth Release Candidate

Release and security announcements
1

Hi,

The OpenWrt community is proud to announce the fourth release candidate of the upcoming OpenWrt 23.05 stable series.
OpenWrt 23.05.0-rc4 incorporates over 4200 commits since branching the previous OpenWrt 22.03 release and has been under development for over one year.

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

Download firmware images using the OpenWrt Firmware Selector:

Changes between OpenWrt 23.05.0-rc3 and 23.05.0-rc4

Changes in this release candidate since the previous 23.05.0-rc3 release candidate are:

  • New devices
    • ipq4019: ZTE MF287 Pro aka DreiNeo Pro
    • mediatek: Ubiquiti UniFi 6 LR v3
    • ramips: ALFA Network AX1800RM
  • Updated components:
    • kernel: Update from 5.15.127 to 5.15.132
    • mt76: Updated from 2023-07-26 to 2023-08-14
    • hostapd: Update from 2023-06-22 to 2023-09-08
    • ucode: Update from 2023-04-03 to 2023-06-06
    • ubus: Update from 2022-06-15 to 2023-06-05
    • netifd: Update from 2023-06-04 to 2023-09-19
    • wireless-regdb: update from 2023.05.03 to 2023.09.01
    • openssl: Update from 3.0.10 to 3.0.11
  • mediatek: lots of backports from master
  • ipq806x: Fix traffic speed regression
  • mac80211: rework MT7620 PA/LNA RF calibration
  • kernel: enable vfio and vfio-pci for armsr-armv8
  • ath11k: Revert back ath11k firmware to fix IPv6 multicast problems
  • kernel: allow adding devices without hw offload to a hw flowtable
  • kernel: backport support for renaming netdevs while up
  • hostapd: backport from master, including ucode based reload support
  • packages: Add many PKG_CPE_ID attributes

Many other changes in all parts of OpenWrt, see Changelog for details.

Highlights in OpenWrt 23.05.0:

Many new devices added

OpenWrt 23.05 supports over 1794 devices. Support for over 200 new devices was added in addition to the device support by OpenWrt 22.03.

  • The ipq807x target for the Qualcomm IPQ807x Wifi 6 SoCs was added
  • The mediatek/filogic subtarget for the Mediatek Filogic 830 and 630 SoCs was added
  • The sifiveu target for the HiFive RISC-V Unleashed and Unmatched boards

Highlights of device support

  • Switched ipq40xx target to DSA
  • VDSL support on AVM FRITZ!Box 7530
  • Support for devices with 2.5G PHYs
    • Acer Predator W6 (MT7986A)
    • Mercusys MR90X v1 (MT7986BLA)
    • Netgear WAX206 (MT7622)
    • Netgear WAX220 (MT7986)
    • ZyXEL NWA50AX Pro (MT7981)
    • Asus (TUF Gaming) AX4200 (MT7986A)
    • Netgear WAX218 (IPQ8074)
    • Xiaomi AX9000 (IPQ8074)
    • Dynalink DL-WRX36 (IPQ8074)
  • 2 Gbps WAN/LAN NAT Routing on ramips MT7621 devices
  • Improved DSL statistics on ubus and in LuCI

Switch from wolfssl to mbedtls as default

OpenWrt switched the default cryptographic library from wolfssl to mbedtls. This library is used for HTTPS/TLS in the Webserver providing LuCI and for the cryptographic operations in hostapd. mbedtls provides security updates in their LTS branch without changing the application binary interface (ABI) of the library. wolfssl provides a stable ABI only for a very limited subset of functions. mbedtls allows us to update only mbedtls without the need to recompile and upgrade all users of mbedtls.

Core components update

Core components have the following versions in 23.05.0-rc4:

  • Updated toolchain:
    • musl libc 1.2.4
    • glibc 2.37
    • gcc 12.3.0
    • binutils 2.40
  • Updated Linux kernel
    • 5.15.132 for all targets
  • Network:
    • hostapd master snapshot from September 2023
    • dnsmasq 2.89
    • dropbear 2022.82
  • cfg80211/mac80211 from kernel 6.1.24
  • System userland:
    • busybox 1.36.1

Full release notes and upgrade instructions are available at
https://openwrt.org/releases/23.05/notes-23.05.0-rc4

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

For a detailed list of all changes since 23.05.0-rc3, refer to
https://openwrt.org/releases/23.05/changelog-23.05.0-rc4

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

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

Have fun!

The OpenWrt Community

20 Likes
3

After ~40 day uptime from rc3 I flashed rc4 on my WRT32X. Added lots of typical packages. It's running great so far thanks devs!

2 Likes
4

Gave 23.05.0-rc4 a try on a pi zero W, configured as a wifi station (not AP).

The default gateway route did NOT get set up after a reboot ! So, the pi was accessible from its immediate subnet, but not from the rest of my homelab.

Few things I tried:

  • setting up explicit IPv4 routes did not work either - the routes were not set up after a reboot
  • running /etc/init.d/network restart did set up the gateway route as expected, so the /etc/config/network seems fine - but the route still does not get set up on its own after a reboot.

guess I'm back on 22.03 until the next 23 rc :slight_smile:

5

Great work. Thanks for the great product!

1 Like
6

Running on WRT3200ACM for 24hrs. So far so good. Many thanks to the Devs!!! :+1:

3 Likes
7

TP-Link CPE210 RSSI LEDs not working

8

Fixed MX60 Halting on Boot, before the Kernel starting.

1 Like
9

I used the Firmware Selector. 802.11s meshes and batman.

Xiaomi AX3600, AX9000, and also ZyXEL WSM20 seem to work normally.

I fixed the /etc/config/wireless (extra non existing radios) in my wax206 and they work also.

1 Like
10

Netgear WAX202, used as a WDS repeater: I did an attended sysupgrade from -rc3, it works (as evidenced by this message), but it took a whole minute to associate.

Packages
Logs

11

Linksys E8450 (UBI). 23.05-RC4 works as expected. Thank you to all developers who contributed to this release.

Did you wait for the DFS radar detection time to complete? This is one minute after boot.

1 Like
12

Reads like standard DFS radar detection wait time.

The log mentions nothing about DFS, and channel 153 is not a DFS channel here in the Philippines. Besides, it is impossible in OpenWrt to run a repeater on a DFS channel.

13

still no love for lantiq xrx200 gswip driver and its pull

4 Likes
14

Archer C60 v2 has broken network.
I can't connect to anything except LAN devices.
Even if I ping an IP address, I get "ping: sendto: Network unreachable"
Reverted to RC3 where everything works flawlessly.

Now I found the problem. The default gateway isn't set after reboot. If I restart WWAN the problem is solved.

1 Like
15

Dynalink DL-WRX36
using attended sysupgrade from rc3 (with ~35day uptime) to rc4.

I did notice the ath11k firmware in rc4 has been reverted to WLAN.HK.2.9.0.1-01385.

I still had to use the wireless option multicast_to_unicast_all '1', otherwise unable to ping, and access shares on various devices.

Thumbs up :+1: to all involved!

16

This is a device with 8 MB flash and 64 MB memory: https://openwrt.org/toh/tp-link/archer_c60_v2

So the 8/64 warning applies for this device: https://openwrt.org/supported_devices/864_warning

I would check if it’s not a simple low resource problem with out of memory or no space left on device errors.

3 Likes
17

This could be the same problem as I reported above, with the default gateway route not being created after reboot. If it is, /etc/init.d/network restart would fix the issue - that is, until the next reboot....

19

I tried, but that isn't the problem.
If you like, you can help me in this post

20

I know it has only 64MB of memory but no additional packages is installed and it works flawlessly with RC3.
I think that differences between RCs are only for bug fixing.

21

@hauke Thinks to add to the list of changes. (we have compat version in place but it was reported that it would be good to add this to the 23.05 changelog)

"ipq40xx EA6350v3, EA8300, MR8300 and WHW01 require tweak to the uboot env on update from 22.xx to 23.xx. Refer to the Device wiki or the instruction on sysupgrade on how to do this change. Config needs to be reset on sysupgrade."

@badulesia maybe can better explain this

4 Likes