Upgraded Archer C50, Fritz!Repeater 1200 and Asus RT-AX53U.
Archer and Repeater seem to work as before. Asus had issues with WAN before, which are still present 23.05.0 Update breaks WAN - RT-AX53U/1800U - #40 by fireburner)
I noticed that the material theme seems to be broken (blue color is missing) on Archer and Asus, but not on the Fritz!Repeater.
I lot of kmod-packages can't be installed because they need a newer kernel version.
Even after a fresh install, there are many updates that can't be. I don't think the release is quite ready guys.
Updated Netgear WAX202 (being used as dumb AP) via Luci's attended Sysupgrade - all seemed to have gone smoothly but then noticed the WAN interface running at only 100M whereas had been running at 1G on 23.05.2. Confirmed it was running slow with quick speedtest, giving me ~93M whereas had been ~300M before. Reboot did not resolve.
No great shakes, just used firmware selector to get a fresh 23.05.2 package which when installed knocked my WAN interface back up to 1G, and then I used Luci's attended sysupgrade again to upgrade a second time to 23.05.3 and this time round the WAN is back to 1G. No idea what the error was, and was reasonably easy to resolve so just including this in case anyone else faces the same.
Apologies if this has been answered already elsewhere, and no criticism because this project rocks, but I've noticed that each time I do a upgrade it keeps most of my settings but it re-enables dnsmasq and firewall in the startup menu (disabled due to being dumb AP). Is that something I can mitigate (aside from just remembering to go back in and switch them off after an upgrade)?
Thanks to the developers, great work and for the moment seems stable.
Happens to my Cudy X6 every now and then on reboot/upgrade. Another reboot usually resolves the issue. Both devices are mt7621 based.
Upgraded both of my actively used devices.
Netgear WAX202: no problems
Linksys E8450 UBI: quite a lot of stuff that I experimented with in the past, so the upgrade was a bit bumpy. But it works now!
I have a theory with 'puters not working right at times. I reckon it's static electricity, some people carry too much of it, and I think I'm one of those.
PPPoE software flow offloading was very fast with OpenWrt 21 (gigabit capable).
Since 22.03.0 it is broken and still not fixed in this latest version 23.05.3, even though there are patches available that haven't been merged:
This released yesterday and I just said "forget it, I'll wait on making a travel router until everything catches up".
Not to mention I'm not upgrading my Pi router (even though I can just swap cards if things go sideways) until everyone is happy.
I don't even do Apple upgrades the day they come out until I read, from reliable sources, it won't cause issues.
I downloaded this release for my TP-link re200v1 using the firmware selector. But it bricked my device. I had to crack it open and use a serial connection to get it working again.
The boot process hangs on the 'starting kernel' stage.
This is remarkable: same device, different results.
So, what was different in the upgrade? Luci's attended Sysupgrade?
In all earnest; a legit question.
Updated EA8300 to the new release.
Saved settings, and everything is running well.
Edit: Update was done using Attended system upgrade.
Ken
KD8DWO
With WPA3 now supported with mwlwifi
is the following still true?
P.S. I have a WRT1900ACS v1
A 1 Gb connection dropping to 100 Mb implies a bad network cable.
@LilRedDog I don't think it's a bad network cable because re-installing the firmware resolved it, and I've not had an issue with that same cable before. Alas now it's resolved I wouldn't know how to work it out but piaddic7ed noted in OpenWrt 23.05.3 - Service Release - #24 by piaddic7ed that he's had similar issues on a similar SOC but resolved with a reboot, so it remains a mystery to me.
I've been watching since the upgrade, the targets have all been posted, but overview.json and packages directory are still missing.
https://sysupgrade.openwrt.org/json/v1/releases/23.05.3/targets/ It's there
https://sysupgrade.openwrt.org/json/v1/releases/23.05.3/overview.json Missing
https://sysupgrade.openwrt.org/json/v1/releases/23.05.3/packages/ Missing
Perhaps @aparcar just needs to give the server a poke?
EDIT The symptom is that (at least) auc can't proceed:
$ auc -c
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)
Probably not, but more interestingly cosmic rays is actually a real issue in computing.
Upgrading my Fritz! 7360 SL (from 23.05.2 to 23.05.3) seems to have impacted my wireguard connection.
Now the Wireguard Status page shows "No WireGuard interfaces configured.", but on the interface page it shows the interface is up (and has been for 3 hours). However, with 0 packets sent/received and the remote network isn't available. After restarting the interface, the Status page shows the interface and the remote network is available.
Try clearing your cache and/or Ctrl+F5, I've seen this happen to the theme in previous sysupgrades.
I did a sysupgrade to 23.05.3 (from 23.05.2) on R6900v2 as AP (MT7621AT - same FCC ID PY316200344 as Nighthawk AC2100 & AC2400, R6700v2, R6800, and R7450). Everything is fine except my ksmbd USB share shows up empty on clients. I can un- and re-mount it, LUCI shows the correct size and usage, and via SSH I can see the /mnt USB contents as expected - nothing on the client though. I also tried reboot, various other mount settings, etc. to no avail.
I then tried the latest snapshot sysupgrade and that bricked it (no serial connected to check what happened, but there were a bunch of static orange LEDs). After nmrpflash recovery, 23.05.02 factory install and setup, the share shows up fine again. I haven't seen any other similar reports yet - anyone else having ksmbd issues?
I'll give it a try next days after I set up my new MT6000. I was still rocking an old OpenWRT version with my WRT3200ACM because of the Switch/VLAN/DSA issues and I never saw anyone stating that all those issues were fixed for mvebu.