Even though ksmbd doesn't appear to have changed going from 23.05.2 to 23.05.3, when I did the sysupgrade, it broke the root directory presentation of the samba share. All subdirectories will show their directories and all data is accessible, but the root of the share won't show a directory listing... you can manually navigate to a subdirectory if you type it in and everything works fine below there, but the root won't present a directory to you via SMB.
3 Likes
I just upgraded my "managed switch" E4200v2 without issues. My APs, router and other switch will follow in due course.
Thx devs
I have updated my QHora-322/IEI PUZZLE-M902 (from 23.05.2)
No problems so far - everything is fine
thx
Upgraded just fine on mine:
Model Linksys WRT3200ACM
Architecture ARMv7 Processor rev 1 (v7l)
Target Platform mvebu/cortexa9
Firmware Version OpenWrt 23.05.3 r23809-234f1a2efa / LuCI openwrt-23.05 branch git-24.073.29889-cd7e519
Among other devices. All of which also upgraded fine.
Edit: DSA has worked 'correctly' for a few versions now. Though AFAIK it's still limited to one NIC and hence one CPU core.
2 Likes
Apparently this has been fixed in the development ("main") branch:
Nice. I did try my Unifi 6 LR on snapshot today but rolled it back to 23.05.3, and it looks like it kept the dnsmasq and firewall disabled when doing that so good news. All appears to be working well so far on the U6 LR. Thanks Devs
I upgraded my Netgear R7800 successfully with this Service Release today.
Finally upgraded WRT3200ACM / EAP-615-Wall
All good 
2 Likes
A word of caution. I have not looked further into this, but my attempts to do an attended-sysupgrade on 3 different x86 devices failed, resulting non-bootable devices. All were on 23.05.2 with the same config and were all survived multiple attended-sysupgrade before.
- From Lenovo mini PC:
Error 1962, no OS found. - From no name Coreboot devices:
Booting from drive failed: verify it contains a 64-bit UEFI.
Working on reinstalling the firewall from scratch now. For my AP, I will try normal file-based sysupgrade instead of attended, hopefully they won't brick.
2 Likes
Updated my Fritz 7360 SL to 23.05.3 (from 23.05.2).
There seems to be a problem with wireguard client.
The status page shows
## WireGuard Status
*No WireGuard interfaces configured.*
When I restart the wg interface, it will show up (and work) for some time but eventually disappear again.
Reverting back to 23.05.2 ‘fixes’ this.
EDIT: Reverting doen’t fix it. I’ll try a clean install (on 23.05.3)
EDIT2: Clean install works great, wg interface stays up.
Oh one thing i noticed, that if i install usteer on that switch that part of the information received from the APs is incorrect. This likely causes it to not function fully correctly. I guess this is due to a change in hostapd? Hence maybe also affects dawn?
Can anybody confirm?
How were you able to update in the first place? 
I'm constantly receiving error 61 "No data available".
Log
root@openwrt-vm:~# auc -n
auc/0.3.2-1
Server: https://sysupgrade.openwrt.org
Running: 23.05.2 r23630-842932a63d on x86/64 (generic)
Available: 23.05.3 r23809-234f1a2efa
Requesting package lists...
No data available (61)
Dynalink DL-WRX36 sysupgrade
23.05.2 => 23.05.3
using firmware-selector image, keeping settings.
All OK! 
2 Likes
Archer c6v3
25.05.2 -> 25.05.3
cant access the router after updating. Second time i experience this after a sysupgrade, any1 know how to fix this annoying problem???
1 Like
Thank you for this release, long life OpenWrt!!!
i´m trying to upgrade my wrt3200 , i´m trying to use attended sysupgrade both cli and gui,
web i cant upgrade to 23.05.3, all i see is 23.05.2 and that version i´m allready on
cli says
root@OpenWrt:~# auc
auc/0.3.2-1
Server: https://sysupgrade.openwrt.org
Running: 23.05.2 r23630-842932a63d on mvebu/cortexa9 (linksys,wrt3200acm)
WARNING: cannot determing currently running branch.
Invalid argument (22)
root@OpenWrt:~# ping sysupgrade.openwrt.org
PING sysupgrade.openwrt.org (206.81.21.114): 56 data bytes
64 bytes from 206.81.21.114: seq=0 ttl=51 time=34.979 ms
^C
--- sysupgrade.openwrt.org ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 34.979/34.979/34.979 ms
EDIT: web
No upgrade available
The device runs the latest firmware version 23.05.2 - r23630-842932a63d
"
ideas?
1 Like
How did you fix it the first time?
What packages did you install on 25.05.2?
How did you do the update?
23.05.2 => 23.05.3 with Attended Sysupgrade
Raspberry Pi CM4
TP-Link EAP615
Updated main router WRT1900ACS and 3 x WSM20 AP's from 23.05.2 to 23.05.3.
After updating, the WRT1900ACS 5 GHz was not active, the channel number (161) was blank. After re-selecting the channel and restarting the radio all is OK.
No issues on the WSM20s.
1 Like
Was that just a Day 0 thing? Not seeing anyone else mentioning it.