OpenWrt 23.05.4 - Service Release

Release and security announcements
61

Not sure what (if anything) is broken specifically because of docker, but the packages seem reachable for me, for example:

$ curl -iI https://downloads.openwrt.org/releases/23.05.4/targets/mediatek/mt7622/packages/kmod-nf-flow_5.15.162-1_aarch64_cortex-a53.ipk
HTTP/2 200 
server: nginx
content-type: application/octet-stream
last-modified: Wed, 17 Jul 2024 03:45:38 GMT
etag: "66973e62-3f11"
access-control-allow-origin: *
access-control-allow-methods: GET, POST, OPTIONS
access-control-allow-headers: DNT, X-CustomHeader, Keep-Alive, User-Agent, X-Requested-With, If-Modified-Since, Cache-Control, Content-Type, Content-Range, Range
via: 1.1 varnish, 1.1 varnish
tmp-path: 
accept-ranges: bytes
date: Sun, 21 Jul 2024 17:49:43 GMT
age: 3729
x-served-by: cache-fra-eddf8230122-FRA, cache-bfi-kbfi7400064-BFI
x-cache: HIT, HIT
x-cache-hits: 293, 2
x-timer: S1721584184.613352,VS0,VE0
alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400
content-length: 16145
62

Just upgraded all of my 3 devices:

  • ZyXEL NWA50AX Pro
  • Linksys WRT3200ACM
  • D-Link DIR825B1

from .3 to .4 via ASU from Luci with my mobile phone while sipping scotch on the porch in a nice, warm summer evening. Don't see anything alarming in the logs. This product is just something commercial software can only dream about. Thanks everyone involved for making this possible!

5 Likes
63

If it was previously updated by script, that script has not been run since 23.05.1 release as I manually updated devices to 23.05.3 and was just about complete when 23.05.4 was released. I've started to update to 23.05.4 but it will take quite a bit of time!

1 Like
64

After a successful upgrade on a different device, I had an odd experience with an attended sys upgrade with an Asus OnHub. At first, it appeared to be a brick situtation.
Everything seemed to be normal with the upgrade process. The device restarted, there were the normal two audible tones, and the LED went through the normal color changes to a solid green.
The computer had a wired connection to the single LAN port of the device.
The computer's NIC status indicator icon in the system tray was spinning as waiting for DHCP, but eventually would timeout to a red-x / not connected status. Then the status indicator would again spin, again timing out to show a red X / not connected status.
I waited for a couple of minutes and eventually the PC's NIC status icon finally showed connected. The PC however received a WAN IP address instead of a LAN IP. It was as if the LAN/WAN ports on the device were bridged, acting as a switch.
At that point I power-cycled the Asus. It then came up normally and was functional.

1 Like
65

Yeah, oddly enough running wget with the failing URL manually inside the Docker container also succeeds for me. I'm thinking maybe the script appends some arguments that my version of wget chokes on…

66

Thanks @efahl so if I’m understanding it right, the correct way is,

  • Unmount the drive
  • Run attendedsysupgrade
  • after updating remount the drive

Is that how it should be? No formatting needed on the usb drive?

67

Normally you'd log in via ssh, do opkg update && opkg install auc then run auc to do the upgrade, no messing with mounts.

auc will collect a list of all the packages on your machine, submit a build request to the ASU server for an image containing all those packages, then install the resulting image. The install process uses the "retain configuration" options of sysupgrade, so when the device reboots, it should look as it did before, but with the new versions of the OS and packages.

68

WRT3200acm upgrade with a WAX620 WiFi AP...no issues. Thanks to the Devs!!!

2 Likes
69

Updated Linksys EA8500 yesterday from .3 to .4 via Attended Sysupdate, keeping all settings.
All went well.
The only thing I've noticed is that 5GHz wireless shows Bitrate maxing out at 433Mbps where before it was over 700.
My clients seem to connect faster than 433 - laptop at 867 for instance, regadless of 433 max reported.

2 Likes
70

Upgraded my Netgear WNDR3700v4 from 23.05.3 to 23.05.4 using the downloaded bin file - flawless as usual. Thankyou everyone for the work you put into this release.

2 Likes
71

Thank you! I tried via the firmware selector before and it didn't show anything.

Looking forward to testing it now :slight_smile:

72

5 posts were split to a new topic: OpenWrt 23.05.4 on the WNDR3700v5/ mt7621st

73

I updated my two (dump) access points yesterday evening: D-Link Covr 1860 and a Netgear WAX220 updated from 23.05.3 to 23.05.4 using luci attended sysupgrade. Both devices started normally and are also sending out the signal.
However, I can neither access the Luci web interface nor the devices via SSH. In both cases I get an error message:

CONNECTION REFUSED

I also cannot ping the two devices.

Does anyone have any ideas?

74

Archer A7 v5: Regular sysupgrade (keep settings) - initially failed to install / reverted to 23.05.3; second attempt successful; no issues
Virtual x86/64 LXC (Jenkins build): Re-install and manual settings import from old install; no issues

Thanks! Now here's to hoping for the next release being major and including DSA for ath79

75

Oh, I do have some wishes, too :wink: Since Mbed TLS 2.28.8 has support until the end of this year, we hopefully go up to the next long term release 3.6 in the next openwrt major release. I am looking forward TLS 1.3 support in openvpn without the need for openssl to save space... Ok, offtopic. A big thanks to all devs.

1 Like
76

Upgraded WNDRMACv2 (WNDR3800) from the last build successfully. Nothing notable so far.

77

I updated 1 Zyxel EX5601-T0 ubootmod (Odido T-56)
and 2 TP-Link Deco M4R v1 (actually v2) devices without any issues.

my other openWRT devices are offline because I have to replace some wires, therefor I haven't updated them yet.

78

FWIW, I had an issue with a resize performed manually via the [HOWTO] Resizing root partition on x86 (March 2023 edition) (see [HOWTO] Resizing root partition on x86 (March 2023 edition) - #50 by rkboni), but once I fixed the partition UUIDs I was able to upgrade and the disk was auto-resized without any problems via https://openwrt.org/docs/guide-user/advanced/expand_root.

Just to confirm, I ran fsck.ext4 -n /dev/sda2 and got a clean bill of health.

Is your partition setup correct, without anything overlapping? Could your drive be going south? Do you have memory issues? (just thinking of common causes of FS corruption). At least it doesn't seem like a generic issue.

79
1 Like
80

Happy to report that I got my first OpenWRT upgrades done without (many) problems. LuCI Attended Sysupgrade didn't work on either x86_64 (Proxmox VM) or ipq806x (Meraki MR-52), but auc worked great on both!

Thanks, all!

Now if I could only upgrade my SNAPSHOT build on another MR-52, that would be great (owut gives ERROR: Firmware revision mismatch: expected r26977-f2f428c699, but got r26990-06b37a5856, so maybe upgrade servers are lagging behind build servers due to the 23.05.4 release?).