OpenWrt 23.05.0-rc3 - Third Release Candidate

Release and security announcements
151

Between last night & today, installing a Firmware Selector custom build on a GL.iNet GL-MV1000, it appears libubus has perhaps been updated to libubus20230605, but some other packages still depend on an older libubus, such as block-mount.

I was using the block command with custom builds of 23.05-rc3 downloaded from Firmware Selector last night and it worked, with a build downloaded today, it does not work:

root@OpenWrt:~# block detect
Error loading shared library libubus.so.20220615: No such file or directory (needed by /sbin/block)
Error relocating /sbin/block: ubus_free: symbol not found
Error relocating /sbin/block: ubus_lookup_id: symbol not found
Error relocating /sbin/block: ubus_connect: symbol not found
Error relocating /sbin/block: ubus_invoke_fd: symbol not found

root@OpenWrt:~# opkg list-installed | grep ubus
libubus20230605 - 2023-06-05-f787c97b-1
ubus - 2023-06-05-f787c97b-1
ubusd - 2023-06-05-f787c97b-1
ucode-mod-ubus - 2023-06-06-c7d84aae-1
uhttpd-mod-ubus - 2023-06-25-34a8a74d-1

Edit: Also, attempting to specify libubus20220615 in Firmware Selector package list is not a usable workaround, as only libubus20230605 is installed in the resulting image.

Edit 2: Apparently a known issue.

152

Netgear GS308T switch works well. The LEDs are working without the
fw_setenv bootcmd "rtk network on; boota"
fix needed for 22.03.

Also have a WRT3200ACM with 1G PPPOE WAN and am testing another WRT3200ACM with 3 VLANs, no problems and great performance. Many thanks.

1 Like
153

that topic is imagebuilder only not firmware selector.

1 Like
154

Yesterday I published the list of upgradable packages that we don't have to upgrade. (base on rc3). Otherwise the router will brick, application wil crash, network shutdown...

Here is the list with "opkg list-upgradable" command.

wpad-basic-mbedtls - 2023-06-22-599d00be-1.2 - 2023-09-08-e5ccbfc6-3
ubus - 2022-06-15-9913aa61-1 - 2023-06-05-f787c97b-1
ucode-mod-ubus - 2023-04-03-51638672-1 - 2023-06-06-c7d84aae-1
ucode-mod-uci - 2023-04-03-51638672-1 - 2023-06-06-c7d84aae-1
netifd - 2023-06-04-ec9dba72-1 - 2023-09-15.1-afcd3825-1
ubusd - 2022-06-15-9913aa61-1 - 2023-06-05-f787c97b-1
ucode-mod-math - 2023-04-03-51638672-1 - 2023-06-06-c7d84aae-1
ucode-mod-fs - 2023-04-03-51638672-1 - 2023-06-06-c7d84aae-1
ucode - 2023-04-03-51638672-1 - 2023-06-06-c7d84aae-1
libucode20220812 - 2023-04-03-51638672-1 - 2023-06-06-c7d84aae-1
hostapd-common - 2023-06-22-599d00be-1.2 - 2023-09-08-e5ccbfc6-3

and as you can see, the "opkg list-installed | grep ubus" command you typed corresponds to these upgradable packages.
consequently --> Badaboom

155

and as you can see, the "opkg list-installed | grep ubus" command you typed corresponds to these upgradable packages.
consequently --> Badaboom

I don't understand enough about the build/release process to know what this means.

I set up an OpenWRT build box last night and am experimenting trying to build the image myself to get around the problems with Firmware Selector.

Is there any way to tell when 23.05.0-rc3 images downloaded with Firmware Selector will once again not ship with broken packages?

Edit: I successfully set up an OpenWRT build box, built a 23.05-SNAPSHOT image for the GL-MV1000, and flashed it, and it does not have the problem I was originally complaining about with the image from Firmware Selector. It sounds like that's exactly what you'd expect, but FYI anyway. I still don't really understand the build process yet but that's fine for now :smile:

156

...I must have posted that right around the time I started thinking Firmware Selector and Image Builder were the same :blush:

I'm still very new to getting my OpenWRT images any other way than downloading pre-compiled from a given URL - even Firmware Selector is still pretty new to me.

157

Hi

23.05-rc3:
Three MR8300, AP only, wired backhaul, 802.11r, wifi up/down works, no issues, works great.

RPi4, router on a stick, still has kernel crash, using the following workaround in /etc/rc.local: /usr/sbin/ethtool -K eth0 rx off, otherwise it works great

WRT1900ACSv2, using a configuration similar to #2, multiple bridged networks, it works great.

However, if using a configuration similar to #3, multiple networks using VLANS, android phones acquires IPv6 addresses from other subnet. Windows clients acquire IPv6 addresses normally. VLANs are still leaking.

Currently running the WRT1900ACSv2 on testing kernel 6.1.52, no issues running #3, multiple networks using VLANS.

158

Where does one search and report bugs for an RC like this?

Thanks.

159

This looks like a good place: https://github.com/openwrt/openwrt/issues?q=is:open%20label:release%2F23.05%20sort:updated-desc

160

I don't understand enough about the build/release process to know what this means.

Neither have I, and I've given up trying to understand, I leave that to the "experts".

161

I used auc to update my software packages tonight and the following updated packages disabled wireless on my Belkin RT3200. I tested by installing all the other packages individually and everything works just fine until I update any / all of the following three packages:

netifd	2023-06-04-ec9dba72-1 » 2023-09-15.1-afcd3825-1
hostapd-common	2023-06-22-599d00be-1.2 » 2023-09-08-e5ccbfc6-3
wpad-mbedtls	2023-06-22-599d00be-1.2 » 2023-09-08-e5ccbfc6-3

Just thought I would let everyone know. If there's a better place to alert the developers, just let me know and I will post there.

Thanks for everything you all do to make such great router firmware!

2 Likes
162
2 Likes
163

hostapd bug?

1 Like
164

i updated the packages and now, i cannot use the wifi anymore, this is the error:

Fri Sep 22 09:23:43 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy phy0-ap0) --> new PHY
Fri Sep 22 09:23:43 2023 daemon.err hostapd: Line 23: unknown configuration item 'radio_config_id'
Fri Sep 22 09:23:43 2023 daemon.err hostapd: 1 errors found in configuration file '/var/run/hostapd-phy0.conf'
Fri Sep 22 09:23:43 2023 daemon.err hostapd: Failed to set up interface with /var/run/hostapd-phy0.conf
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217): Command failed: ubus call hostapd config_add {"iface":"phy0-ap0", "config":"/var/run/hostapd-phy0.conf"} (Invalid argument)
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217): Usage: ubus [<options>] <command> [arguments...]
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217): Options:
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  -s <socket>:		Set the unix domain socket to connect to
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  -t <timeout>:		Set the timeout (in seconds) for a command to complete
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  -S:			Use simplified output (for scripts)
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  -v:			More verbose output
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  -m <type>:		(for monitor): include a specific message type
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217): 			(can be used more than once)
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  -M <r|t>		(for monitor): only capture received or transmitted traffic
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217): Commands:
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  - list [<path>]			List objects
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  - call <path> <method> [<message>]	Call an object method
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  - subscribe <path> [<path>...]	Subscribe to object(s) notifications
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  - listen [<path>...]			Listen for events
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  - send <type> [<message>]		Send an event
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  - wait_for <object> [<object>...]	Wait for multiple objects to appear on ubus
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):  - monitor				Monitor ubus traffic
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217):
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7217): Device setup failed: HOSTAPD_START_FAILED
Fri Sep 22 09:23:43 2023 daemon.notice netifd: Wireless device 'radio0' set retry=0
Fri Sep 22 09:23:43 2023 daemon.crit netifd: Wireless device 'radio0' setup failed, retry=0
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7354): WARNING: Variable 'data' does not exist or is not an array/object
Fri Sep 22 09:23:43 2023 daemon.notice netifd: radio0 (7354): Bug: PHY is undefined for device 'radio0'
Fri Sep 22 09:23:43 2023 daemon.notice netifd: Wireless device 'radio0' is now down
Fri Sep 22 09:23:45 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses

please help!

165

hostapd does not know what to do with this.

If you don't use 802.11r (FT / roaming) then you can delete this or use a workaround.

or rollback

166

how can i can delete this radio_config_id? it is generated somewhere.

167
2 Likes
168 
auc -b 23.05 -B 23.05-SNAPSHOT

See if it's fixed in the latest snapshot

auc -b 23.05 -B 23.05.0-rc3

to go back, you can also go to rc2 if required.

1 Like
169

Won’t that install the latest package versions from head non the less?

1 Like
170

On my wrt1900acs netifd - 2023-06-04-ec9dba72-1 - 2023-09-19-7a58b995-1 works fine. Not updated yet hostapd-common or wpad-basic-mbedtls .

FYI