OpenWrt 22.03.0 first stable release

Hi,

The OpenWrt community is proud to announce the first stable release of the OpenWrt 22.03 stable version series. It incorporates over 3800 commits since branching the previous OpenWrt 21.02 release and has been under development for about one year.

Download firmware image for your device (firmware selector):
https://firmware-selector.openwrt.org/?version=22.03.0

Download firmware images directly from OpenWrt download servers:
https://downloads.openwrt.org/releases/22.03.0/targets/

Highlights in OpenWrt 22.03.0

Firewall4 based on nftables

Firewall4 is used by default, superseding the iptables-based firewall3 implementation in the OpenWrt default images. Firewall4 uses nftables instead of iptables to configure the Linux netfilter ruleset.

Firewall4 keeps the same UCI firewall configuration syntax and should work as a drop-in replacement for fw3 with most common setups, emitting nftables rules instead of iptables ones.

Including custom firewall rules through /etc/firewall.user still works, but requires marking the file as compatible first, otherwise it is ignored. Firewall4 additionally allows to include nftables snippets. The firewall documentation explains how to include custom firewall rules with firewall4. Some community packages that add firewall rules might not work for now, and will need to be adapted to fw4: this will happen gradually throughout the lifetime of the 22.03 release series.

The legacy iptables utilities are not included in the default images anymore, but can be added back using opkg or the Image Builder if needed. The transitional packages iptables-nft, arptables-nft, ebtables-nft and xtables-nft can be used to create nftables rules using the old iptables command line syntax.

Many new devices added

OpenWrt 22.03 supports over 1580 devices. Support for over 180 new devices was added in addition to the device support by OpenWrt 21.02. OpenWrt 22.03 supports more than 15 devices capable of Wifi 6 (IEEE 802.11ax) using the MediaTek MT7915 wifi chip.

More targets converted to DSA

The following targets or boards were migrated from swconfig to DSA with OpenWrt 22.03 in addition to the systems already migrated with OpenWrt 21.02:

  • bcm53xx: All board using this target were converted to DSA
  • lantiq: All boards using the xrx200 / vr9 SoC
  • sunxi: Bananapi Lamobo R1 (only sunxi board with switch)

Dark mode in LuCI

The LuCI bootstrap design supports a dark mode. The default design activates dark mode depending on the browser settings. Change it manually at “System” -> “System” -> “Language and Style”.

Year 2038 problem handled

OpenWrt 22.03 uses musl 1.2.x, which changed the time_t type from 32 bit to 64 bit on 32 bit systems, on 64 bit system it was always 64 bit long. When a Unix time stamp is stored in a signed 32 bit integer it will overflow on 19 January 2038. With the change to 64 bit this will happen 292 billion years later. This is a change of the musl libc ABI and needs a recompilation of all user space applications linked against musl libc. For 64 bit systems this was done when the ABI was defined many years ago, the glibc ARC ABI already has a 64 bit time_t.

Core components update

Core components have the following versions in 22.03.0:

  • Updated toolchain:
    • musl libc 1.2.3
    • glibc 2.34
    • gcc 11.2.0
    • binutils 2.37
  • Updated Linux kernel
    • 5.10.138 for all targets
  • Network:
    • hostapd 2.10, dnsmasq 2.86, dropbear 2022.82
    • cfg80211/mac80211 from kernel 5.15.58
  • System userland:
    • busybox 1.35.0

In addition to the listed applications, many others were also updated see the detailed Changelog for more information.
https://openwrt.org/releases/22.03/changelog-22.03.0


Upgrading to 22.03.0

Sysupgrade can be used to upgrade a device from OpenWrt 21.02 to 22.03, and configuration will be preserved in most cases. Upgrades from a previous 22.03.0 release candidate are also supported.

  • Sysupgrade from 19.07 to 22.03 is not supported.
  • There is no migration path for targets that switched from swconfig to DSA. In that case, sysupgrade will refuse to proceed with an appropriate error message:
    Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed

Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.0

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

For a detailed list of all changes since 21.02, refer to
https://openwrt.org/releases/22.03/changelog-22.03.0

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

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

Have fun!

The OpenWrt Community


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

a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce

a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14

other announcement channels (such as RSS feeds) might be added in the future, they will be listed at https://openwrt.org/contact

50 Likes

Upnp nftables not working in this release.

1 Like

https://firmware-selector.openwrt.org/?version=22.03.0
Building 22.03.0 does not work:
Unsupported version: 22.03.0

1 Like

It needs to be added to the list manually, so just wait a few hours/ days for it to be listed there.

4 Likes

thanks for all :slight_smile:

I updated my ER-X, now flow_offloading_hw works and allow me to reach 920 Mbps in download and 475 Mbps in upload with my FTTH GPON that has nominal speed of 1 Gbps / 500 Mbps.
Unfortunately this speed can be achieved just separately, contemporary upload and download cause the cut of downlad speed to 2 Mbps while only upload keep the max speed of 475 Mbps. Not sure what is the root cause of the problem.

"Over 3800 commits"! Thank you to all!

8 Likes

Updated total 6 devices from 22.03.0-rc6 to 22.03.0 release:

  1. Belkin RT3200 (UBI) (mediatek/mt7622) (3 devices)
  2. Netgear R7800 (ipq806x/generic) (1 device)
  3. TP-Link Archer A7 v5 (ath79/generic) (2 devices)

Big thank you to all the developers involved in OpenWrt.

1 Like

Hi @openx I was going to update an ER-X tomorrow... have you tried to turn off hardware or both hardware and software offloading to see if that fixes?

Thank you developers!

Please for OpenWrt newbies can a kind soul help advise the following for the benefit of all and the many on RT3200s? @hnyman you are always very glad at explaining these issues?

What's the significance of this for those who were using 22.03 snapshots?

Is it that now packages can be installed or upgraded without needing to first flash the latest snapshot? Can we use something like opkg upgrade now to upgrade packages? Or is that still not advised? Explanation in this confusing aspect welcome!

And is there a command to upgrade to this release using auc? And is then the idea we'd use auc to upgrade to later 22.03 stable releases?

Also how would staying on this release compare with just staying on 22.03 snapshots?

If you are on the 22.03 snapshots (either from buildbot or by building yourself), there is currently not much difference. Currently the 22.03 branch is just 4 commits ahead of the fixed 22.03.0 release. https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog;h=refs/heads/openwrt-22.03

In future, if you want to get the new fixes committed to 22.03 before the next maintenance release 22.03.1, just stay with the 22.03 snapshots.

By itself the release is functionally nothing special. It is just one fixed commit point in the 22.03 branch history.

However, using the fixed official release makes it possible to more easily install additional kmods via opkg.

The "release" status changes nothing regarding "opkg upgrade". Upgrading already installed packages en masse can still cause trouble if some ABI dependencies have changed.

No comments/advice regarding auc, as I build my own firmwares from srcatch, either master snapshots or 22.03 snapshots.

5 Likes

I have upgraded to NETGEAR R7800 (Nighthawk X4S AC2600) a few minutes ago. Looks great, many thanks to the developer community of OpenWrt.

A great job you are doing here

4 Likes

Thanks all for a grate build.

Installed on BT Home hub 5. Running great, only trouble is at boot, can take a few attempts. Maybe this is related to the age of the device more than OpenWRT.
On another brand new device, a Mediatek MT7622 Xiaomi Redmi AX6S it seem fine.
Well done to the development team.

Hi.
Installed successfully on these devices with various configs (router, repeater, AP)

  • Linksys MR8300 (ipq4019 generic)
  • Netgear R6220 (mt7621)
  • Netgear 3700v2 (ath79 generic)
  • x64 (of course)

Nevertheless I will reverse the 3700v2 to 21.03 due to lower memory print, it was just a test.
Huge thank you to every devs and contributors for this major release.

PS : I will install on a Linksys EA7300v2 shortly.

1 Like

Nevertheless I will reverse the 3700v2 to 21.03 due to lower memory print

How bad was the difference and performance? I have the same router and was planning on upgrading.

With hardware and software offloading disabled and packet_stearing enabled as default in network section, the max speed is around 300 Mbps, the contemporary upload and download problem disappear with the total 300 Mbps shared between dl e ul.
Let me know your experience and if you have my same behaviour.

I added it to sysupgrade.openwrt.org

6 Likes

Hi.
I have sereral of these and keep them as spare devices. I don't use them on a regular basis, I have just installed 22.03 as a test. It works, but the memory print is hight (2 MB ?). I can't tell about the performance.
Install it and make your own opinion :wink: