OpenWrt 23.05.0-rc2 - Second Release Candidate

Release and security announcements
145

When I try an attended sysupgrade on a Linksys WRT3200ACM running 22.03.2, I get an error that seems to be about the SSL tool change:

Collected errors:
 * check_data_file_clashes: Package libustream-mbedtls20201210 wants to install file /home/aparcar/asu/worker1/cache/23.05.0-rc2/mvebu/cortexa9/build_dir/target-arm_cortex-a9+vfpv3-d16_musl_eabi/root-mvebu/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:187: package_install] Error 255
make[1]: *** [Makefile:152: _call_manifest] Error 2
make: *** [Makefile:272: manifest] Error 2

Should I try removing wolfssl and adding mbedtls?

I'm a novice at this process, mostly following videos from onemarcfifty. This router has an outstanding vulnerability that prevents upgrading to 22.03.5, but since the image for 22.05.0-rc2 is available, I'm hoping there's a security benefit to upgrading.

146

If attended sysupgrade fails you could instead use the standard sysupgrade procedure.

2 Likes
147

22.03 uses wolfssl while 23.05 uses mbedtls. Hence you can't simply upgrade as the packages list is not the same. Perform a standard sysupgrade instead.
EDIT : Can't !

2 Likes
148

When I try to install ss on 23.05.0-rc2 I get the following error:

Installing ss (6.3.0-1) to root...
Downloading https://downloads.openwrt.org/releases/23.05.0-rc2/packages/x86_64/base/ss_6.3.0-1_x86_64.ipk
Installing libnl-tiny2023-07-01 (2023-07-01-d433990c-1) to root...
Downloading https://downloads.openwrt.org/releases/23.05.0-rc2/packages/x86_64/base/libnl-tiny2023-07-01_2023-07-01-d433990c-1_x86_64.ipk
Collected errors:
 * check_data_file_clashes: Package libnl-tiny2023-07-01 wants to install file /usr/lib/libnl-tiny.so
	But that file is already provided by package  * libnl-tiny2023-04-02
 * opkg_install_cmd: Cannot install package ss.

Is this expected since libnl-tiny has changed? (libnl-tiny2023-04-02 exists in the target files built on Jun 28, and libnl-tiny2023-07-01 exists in the current core packages.) Or is there a problem with libnl-tiny, should both packages be able to coexist on the device? In that case I guess the SONAME of the library should differ.

BTW I tested it on an LXD instance based on the x86-64 rootfs archive.

Edit: It was reported as issue #13082 by someone else.

149

Hi,

Issue with DHCPV6-PD isn't solved.
Seems related to https://github.com/openwrt/odhcp6c/issues/61
I suppose I should file a bug on github ?

1 Like
150

Today updated Archer c7 v4 ip 192.168.1.2 (mesh with Linksys E8450 UBI 192.168.1.1 with WAN (23.05.0-rc1) by ethernet cable) to 23.05.0-rc2 and Luci not working, ping not working, ssh refused.But LAN (wi-fi) is workin. Reset archer and restore backup with connect notebook by ethernet. And again Luci not working, ping not working, ssh refused, but mesh LAN (wi-fi) is working. Why did it happen? Now set everything up again. Now I'm afraid to update Linksys E8450 :slight_smile:

151

23.05.0-rc2 is running well on my E8450 (UBI). Standard sysupgrade procedure.

152

Ubiquiti EdgeRouter-X running well after 'auc' from 23.05.0-rc1

1 Like
153

OK. But I asked what should I do with Archer c7 v4,
which after the new firmware stopped working normally!
not with E8450.

155

With device DSA supported, do i even need swconfig package in firmware build ?

What about "switch" uci section ? Is that the cause for failed sysupgrade ?

156

It would be useful to file a bug in the main openwrt repo, as this seems like it might affect a significant number of users if released.

157

What issue - can you provide a link to where you described it?

No issues with PD here.

158

Thi is a bug?

159

Hi

Bug filed here :

160

With WRT1900ACS, when software flow offloading is enabled in the firewall settings, Ethernet connected devices can't access the Internet. Ping and DNS resolution works fine, but they somehow can't load a web page. SIP phone can't register.

WiFi devices are not affected by this bug.

22.03.2 worked fine with the "software flow offloading" option checked. So it seems it is a regression in 23.05. But I can live with it as my Internet connection is slow anyways.

161

It's troubling to read about all these new WiFi issues in 23.05. Hopefully they will get resolved before the main release.

Does this WDS brokenness affect your RT3200 too?

Have either of you raised an issue on GitHub? Then again there are so, so many outstanding issues there that I wonder whether we should fear for the future of OpenWrt. As those grow and grow they dilute one another further and further.

1 Like
162

I have not tried - too much custom setup on my RT3200 (well, Linksys E8450). Route-based IPSEC VPN for getting a public IP, WireGuard VPN for encrypted connection to my relatives' network in Russia, some non-trivial mwan3 rules for choosing what goes where, and a few modem-related packages not available in stock OpenWrt.

163

Software flow offloading has been broken on mvebu for a while unfortunately. Not sure when it started (DSA? 5.10? 5.15? I forget) but it's been talked about on some of the custom build threads for over a year it feels like. Think it goes mostly unnoticed since so many use SQM. Don't think there is any fix, maybe with 6.1.

3 Likes
164

It should be in the known issues of the release notes then. And maybe even disable the option if it's not going to be fixed.

4 Likes
165

running on Netgear 4300V2 so far stable

image
image1158×698 28.2 KB