SSH does work,
I tried rebooting, but that didn't change anything
I didn't have those issues on RC3,
wifi seems to work, but not 100% sure as I won't update my other accesspoints now.
[edit:]
I used "Customize installed packages and/or first boot script" to have an image without -ct drivers.
but I don't see luci in the default packages
Was that default route even there in previous Zero images?
As of now, the Pi Zero (W) OpenWRT images seemed to have been designed with almost no network in mind (to me kind of unusual for an OpenWRT device. OpenWRT = in my eyes: you want to use it as a network device. And since it has USB and HAT support and no 4MB flash limit, this default config decision seems unexpectedly restricted)
To me this makes the Zero particularly difficult to setup compared to other OpenWRT devices: no built in RJ45, no Wifi on by default (which is usual, but additionally difficult if you cant use LAN either), no USB LAN dongles supported by default, all reasonable OpenWRT default network config content wiped. You only have the plain console.
Currently I create a Zero custom image right away, to prefit it with USB LAN dongle drivers + customized UCI init script to get back the well-known OpenWRT network config file defaults. But once you made it past that steep initialization curve, it is a super nice 1 Watt sensor device + mini server/network device, from my perspective much better than with Raspberry OS.
LuCI is not included on the Firmware Selector list
Additionally, a lot more LuCI packages need to be added to get the "full functionality" in 23.05.0 that LuCI had in older versions. I'm not sure when this actually changed
Another Linksys E8450 (UBI): attempted an attended sysupgrade from 22.03.5, replacing the old variant of wpad with wpad-mbedtls but otherwise preserving the list of packages. Result: no WiFi. Upon inspection, the reason why WiFi failed was the missing WiFi firmware.
The old version had the kmod-mt7615-firmware package, which contained the ROM patches for both mt7615 and mt7622, while in the new version, the mt7622 firmware has been moved to a separate kmod-mt7622-firmware package. Similarly, the mt7915 firmware is now in the kmod-mt7915-firmware package (was in kmod-mt7915e directly).
After installation of the missing firmware packages, the router works - including NFSv4, SAMBA4 (the real one, not the in-kernel version), PPPoE, SQM, USB LTE modem, modem goodies from @IceG, DNS over TLS via Stubby, DAWN, mwan3, StrongSwan for the Ivacy VPN, and a WireGuard site-to-site tunnel.
Yes. I do have an /etc/config/network set up in the image I am using, with option ipaddr setting the host's local address and subnet, and option gateway setting the gateway. When rebooting, openwrt 23.05.0-rc4 creates a subnet route as expected, but does not create a default route, while rc3 created both.
@evoserver here seems to have a similar issue as mine. One common point between our setups is that the problem interface is set up as a wifi station (not AP). I am not sure if that is the cause but it seems suspicious since it's a common point between the two reports.
I agree with your other points about the default pi zero image being hardly usable. I am creating custom images with imagebuilder just like you
Would like to try this version on my Belkin RT3200 but getting the following warning in LuCI:
Cannot open file '/etc/opkg/keys/f4dadee8c9e29584' for reading Image check failed.
The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.
EDIT: This is also happening for me with the latest SNAPSHOT. Probably due to my added packages.
Wondering if anyone else has gotten this message and force updated successfully? Is it safe to force flash or would you not recommend it?
From the release notes:
Sysupgrade can be used to upgrade a device from 22.03 to 23.05, and configuration will be preserved in most cases.
Sysupgrade from 21.02 to 23.05 is not officially supported.
Since the linksys WRTXX00ACM does not have a 22.03 version how are they supported in upgrading from 21.02 to 23.05?
I have a question concerning the 'nas_identifier' in the '/var/run/hostapd-phyX.conf' configuration file. In previous releases, it defaulted to the device's MAC address when left out in the '/etc/config/wireless' configuration. This no longer appears to be the case. Does hostapd now handle this differently behind the scenes, or has it become somehow mandatory with SAE encryption?
Its got to be one of my added packages. I think I will wait for now.
UPDATE: I decided to bite my nails and force flash to rc4 and it was successful except that auc now responds with the following:
Server: https://sysupgrade.openwrt.org
Running: 23.05.0-rc4 r23482-7fe85ce1f2 on mediatek/mt7622 (linksys,e8450-ubi)
Available: 23.05.0-rc4 r23482-7fe85ce1f2
Requesting package lists...
No data available (61)
Anyone else seeing this when checking for updates with auc?
