OpenWrt 23.05.2 - Service Release

Release and security announcements
122

Upgraded my BTHH5 to 23-05.2, retaining the current settings.
Unfortunately the 'Attended Sysuprade' failed, so I had to use the 'Flash new firmware image' utility in '/cg/cgi-bin/luci/admin/system/flash'.
I assume that the error message much repeated in the system log is part of the DSA issue on this target:
"2023 daemon.warn odhcpd[1768]: No default route present, overriding ra_lifetime!" (I have not seen this error before.)

I am on an ADSL service, using PPPoATM protocol. How do I change the configuration to show the 'pppoa-wan' device rather than 'dsl0' in the 'PORT STATUS' display of the status summary page?

123

I've updated to OpenWrt 23.05.2: 2x RT1800, 2x WAX202, 2x DAP-X1860, an MF286D, a GS308T and a 7360 v1. Everything works great. 802.11r roaming works very well, tested in a Google Meet using my older phone (Xiaomi Redmi Note 7 running Android 10), which was a bit lazy roaming with OpenWrt 22.03.

Which for me isn't ideal as I can't stop buying these things! :grinning: ..thankfully they're cheap! :wink: but sysupgrading them all is getting a little cumbersome... :slight_smile: I'm only joking of course.

It goes without saying but I'll say it anyway: a big thank you to all the developers, contributors and testers! OpenWrt is such a brilliant community effort!

Also big kudos to Mediatek. Since I've been using OpenWrt you've become my top choice when buying hardware.

5 Likes
124

I was curious what chipset they used, and it seems most of those routers are mt7621 based with mt7915 Wi-Fi.

Is it something about their compatibility or reliability of that specific chipset that you prefer them?

125

Yes as, albeit old, the MT7621 is a very well supported chip by OpenWrt, including its hardware acceleration, and since 23.05 it supports 1 Gbps routing. With a 1 Gbps line I don't really need QoS, which an MT7621 couldn't do at high speed. Its Wireguard performance is more than adequate for my use, I just use it for remote access.

The MT7915 is also a very well supported chip with frequent updates and its WiFi performance is rock solid. I also thought that having the same WiFi chip on all my APs doing 802.11r would be beneficial to seamless roaming.

I bought the second RT1800 just to have a cold standby router in case of problems with the primary one, especially as at some point I may go remote and then switch to a hot standby setup with keepalived (VRRP), for failover and to run potentially disrupting config changes or firmware updates on the standby router first, then on the primary one. They're cheap anyways and like for like standby devices are well worth having.

2 Likes
126

Anyone else having problems with TPLINK EA225 V3 and V4 with 23.05.X release?

127

23.05.2 upgrade succeeded on an Archer C7 v2
Log is clean as ****, yay!

128

Thank you so much for the reply and for the info!

I'm glad to hear that the support for it is excellent and having the same WiFi is definitely a plus for seamless roaming.

Also, that is a very good suggestion to have a hot standby setup. Thank you for that.

I use an EdgeRouter X with the mt7621 and had very good experience with it, and also a Xiaomi AX3200 with mt7622.

The mt7622 also seems to work great with OpenWrt and might be a viable option as well, as a somewhat faster chipset. However, with Hardware Offload, it doesn't make any difference.

1 Like
129

Yep, I missed the RT3200 (MT7622) EU shore boat so I went with the RT1800, else I would have got the RT3200, but as you said it wouldn't have made any difference as I still wouldn't have used QoS.

It'd have better WiFi but I only have 2x2 clients and not so many, so still no difference. While the RT1800 USB 3 (vs. USB 2 on the RT3200) is useful for the SSD connected to it.

Sorry mods for the off topic, anyway the thread has quieted down since release.

1 Like
130

x86, works well with exhausting overloads
massive adguard (~2mil. items list)
massive crowdsec (about 1.4TB rules)
hardcore irqbalance
custom ruled sqm for 40-60 users
1+Gbit/s 24/7 file sharing/editing/working with samba
with 0 restarts since release, 0 issues! (some warnings ofc, but no heavy issues)

thanks for all the developers, such a great project, and such a great release!

1 Like
131

Unattended upgrade failed on TP-Link Archer C6 v3 from 22.03.5 due to wolftls.
Why mbedtls replaced wolftls?

Collected errors:
 * opkg_install_cmd: Cannot install package luci-i18n-ddns-en.
 * opkg_install_cmd: Cannot install package luci-i18n-watchcat-en.
 * check_data_file_clashes: Package libustream-mbedtls20201210 wants to install file /builder/build_dir/target-mipsel_24kc_musl/root-ramips/lib/libustream-ssl.so
	But that file is already provided by package  * libustream-wolfssl20201210
 * opkg_install_cmd: Cannot install package luci-ssl.
make[2]: *** [Makefile:189: package_install] Error 255
make[1]: *** [Makefile:154: _call_manifest] Error 2
make: *** [Makefile:274: manifest] Error 2
132

https://forum.openwrt.org/t/openwrt-23-05-0-first-stable-release/174239?u=eginnc

2 Likes
133

"TLS 1.3 Support: Users should be aware that mbedtls 2.28 no longer supports TLS 1.3."
...and user can change it. BUT, this way acu cannot deliver automatic upgrade.
Can we replace wolftls in 22.03.5 with mbedtls and execute acu with success or install 23.05.2 and then restore our config?

134

This is the best approach between major version upgrades.

1 Like
135

My umdns problem did not appear to appeal to anyone here :grinning:

I pushed my investigation further. I tried resetting my configuration, in case it was something from my config causing this bug.

From a clean OpenWrt 23.05.2, with only IP configuration after first startup, and installation of only umdns and its dependencies from opkg, I can still reproduce the bug on my Xiaomi Mi Router 3G. So I think my configuration is out of suspicion.

I also have a Buffalo WZR-300HP, which is not an mt7621 device like my other two routers (target ath79/generic). Did the same test on it... umdns works perfectly fine, I cannot reproduce this bug on it. Which makes me think that this bug could be specific to target ramips/mt7621

I filed a bug with the information I gathered: https://github.com/openwrt/openwrt/issues/14120

136

Yes I kept settings, all upgrades i did before the latest, it worked just fine with "keep settings". I am going to buy another router and will test it without keep settings.

137

Sometimes keep settings will work. Sometimes it does not. The developers change the default configuration files from time to time - especially from one major release to another.

For this reason, it is a good idea to make a backup of your configuration and not keep settings when upgrading from one major release version to another (e.g., 22.x.x to 23.x.x). Then manually restore the desired configuration, using your backup as a guide (unless your backup does not apply, e.g., with a major change like swconfig to DSA). Do not just restore the backup, as that would defeat the purpose.

2 Likes
138

Just upgraded from 22.03.3 -> 22.03.5 -> 23.05.2 on my OptiPlex 7050 running x64 EFI. The first point upgrade executed 100% uneventfully but I had to opkg uninstall an old wolfssl package first (don't remember the name) before auc would work. Otherwise, everything else seems to have carried over without issues.

139

Upgraded from 22.03, then I found my 2.5G net card is set to HALF Duplex and cannot be changed, after a ton of research, I think it is a BUG of 23.05, please help to fix it on the next build, please refer to:

Thanks in advance.

141

What do you mean? It comes up right here:

https://firmware-selector.openwrt.org/?version=23.05.2&target=ipq40xx%2Fgeneric&id=linksys_ea8300

1 Like
144

Seems I miss read that there was an upgrade to the current software.
The thread that indicated that can no longer be found on my end.
Case closed.

1 Like