OpenWrt 23.05.0-rc2 - Second Release Candidate

I used the attended sysupgrade for all snapshot images, and the firmware-selector to get onto 23.05.0rc2

I'm using 2x 2.4GHz SSIDs & 2x 5GHz SSID's and WPA2, guest on each.
OK since my last post :crossed_fingers:

Where I described the issue where I cannot ping devices on the same br-lan, restarting the network 'service network restart' fixes this issue. I've only done this within the last hour so I'll see how that pans out. :crossed_fingers:

EDIT: the issue has raised it's ugly head again!

1 Like

With WiFi Roaming beeing broken aswell when DSA is in use it will probably be broken for many people. Also the randomly broken ipq40xx images are fun, you never know if an image ends up bricking your router or if it works. It's not even close to being a stable release yet.

3 Likes

Yep I understand that. Just a bit confused how right before 23.05 tag, everything was rock solid stable. We're getting there.

The randomly broken images have been around for quite a few months already, and so has the DSA connection issue. Maybe a few new issues somehow managed to appear right before the branching, but certainly not all of them.

1 Like

You should add less performance in NAT/Internet due to DSA implementation.

  1. ** Cooling Fan not working after booted**
    using POWER LOGIC pld5010s112L cooling fan 4pin to 2pin
    flashed on NOR using sdcard.img
  2. Requesting scdaemon or pcsc-lite to be pre-installed
  3. Requesting an update to new kernel 6.XX with rust support

the other thread of the guy, who skipped mentioning its a Banana 3 and uses this bug feedback thread for feature requests

3 Likes

That's not going to happen in 23.05, which will release with 5.15 LTS and stay on that kernel for its whole supported lifetime.

The SNAPSHOT/main branch is moving to 6.1 LTS in a piecemeal fashion, but not very fast as many of the devs are working on getting 23.05 ready for release. If you happen to have a platform for which the 6.1 switchover has already been done, then you may find it at https://firmware-selector.openwrt.org/

3 Likes

My BananaPi R3 is working flawless. Using one 2.5gb/s insert on full speed, WiFi with wpa2 both n and ac and also 3 vlans on which network extender is connected which does points dhcp request to Banana. Software runs from sdcard was not able to make it running from emmc. Custom image with build in settings also works no issue. Hope it helps.

2 Likes

I'm trying to test the BPi3 and it seems that the USB port caused the problems as at the same time the USB interface on the UPS broke. Not sure what the root cause was.
I'm now giving it a new try without UPS connected and without crowdsec-firewall-bouncer so I may be able to narrow down my problem. It runs now for 1 day without problems. Fingers crossed.

Upgraded to 23.05.0-rc2 on my Linksys 3200 ACM. I wanted to install luci-app-unbound but there is a conflicting package libnl-tiny2023-04-01 vs what unbound needs libnl-tiny2023-07-01. I also tried to remove the existing libnl-tiny2023-04-01 but it failed.

Executing package manager

Installing luci-app-unbound (git-21.303.32118-fce70a0) to root...
Downloading https://downloads.openwrt.org/releases/23.05.0-rc2/packages/arm_cortex-a9_vfpv3-d16/luci/luci-app-unbound_git-21.303.32118-fce70a0_all.ipk
Installing libnl-tiny2023-07-01 (2023-07-01-d433990c-1) to root...
Downloading https://downloads.openwrt.org/releases/23.05.0-rc2/packages/arm_cortex-a9_vfpv3-d16/base/libnl-tiny2023-07-01_2023-07-01-d433990c-1_arm_cortex-a9_vfpv3-d16.ipk

Errors

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 luci-app-unbound.

The opkg install command failed with code 255.

It's a known bug, you can either wait for -rc3 or build an image with all the packages you need via the firmware selector (also add luci).

3 Likes

I'm happy with my BPiR3 so far. But I have one question about flow offloading.

I have IPTV by IGMP and looking in the conntrack state I find this:

udp      17 src=77.109.129.16 dst=239.77.0.105 sport=5000 dport=5000 packets=1922613 bytes=2583991872 [UNREPLIED] src=239.77.0.105 dst=77.109.129.16 sport=5000 dport=5000 packets=0 bytes=0 [HW_OFFLOAD] mark=0 use=2

While all other entries only have a [HW_OFFLOAD] (or [OFFLOAD] without hardware offload set) at the end of the entry this one also have the [UNREPLIED] state shown.
I haven't found any info on this so I wonder if this is only a partial offloading like only in one direction? The IGMP is the very much most amount of data my BPiR3 has to process so offloading this path would by very welcome.

So what does this entry mean and is the IGMP offloaded?

1 Like

I love the new 'Port Status' section in the Luci overview page. :slight_smile:

4 Likes

Hello.

Is there any constrain to the Xiaomi AX3600 model not being apparently contemplated for the next stable Openwrt release?

Thanks.

Huh, I don't have a "port status"?

1 Like

Hey, you can find it, if you made the latest updates for RC2, on the LUCI Status Menu -> Overview Page ... there is the Port Status Info, newly integrated.
Thanks to developers for this new feature ..Cheers

Nope, not present on RC2 running on my WRT1900 ACS. Perhaps because I upgraded from RC1?

It's on a newer version of the luci-mod-status that has been released a few days ago, you will find it on the software updates list, but don't update it from there. If you want to install it before -rc3 comes out, use the firmware selector and build a new image (add luci and any extra packages you need), it will use all the latest versions of packages. I just did it earlier after I read @ne20002's post. it's indeed very nice.

https://firmware-selector.openwrt.org/?version=23.05.0-rc2&target=ipq807x%2Fgeneric&id=xiaomi_ax3600

1 Like