Install on another xiaomi 4a gigabit router and works well
1 Like
Upgraded Belkin RT3200 using the image from releases/23.05.5/ folder. It works well but my Apple TV box does not like it. In the logs I can see that while sleeping it keeps reconnecting every 2 - 3 minutes. I don't think it happened with the previous releases.
Fri Sep 27 09:12:23 2024 daemon.notice hostapd: wl1-ap0: AP-STA-DISCONNECTED c8:69:cd:0d:21:d2
Fri Sep 27 09:12:23 2024 daemon.info hostapd: wl1-ap0: STA c8:69:cd:0d:21:d2 IEEE 802.11: disassociated
Fri Sep 27 09:12:23 2024 daemon.info hostapd: wl1-ap0: STA c8:69:cd:0d:21:d2 IEEE 802.11: authenticated
Fri Sep 27 09:12:23 2024 daemon.info hostapd: wl1-ap0: STA c8:69:cd:0d:21:d2 IEEE 802.11: associated (aid 2)
Fri Sep 27 09:12:23 2024 daemon.notice hostapd: wl1-ap0: AP-STA-CONNECTED c8:69:cd:0d:21:d2 auth_alg=open
Fri Sep 27 09:12:23 2024 daemon.info hostapd: wl1-ap0: STA c8:69:cd:0d:21:d2 WPA: pairwise key handshake completed (RSN)
Fri Sep 27 09:12:23 2024 daemon.notice hostapd: wl1-ap0: EAPOL-4WAY-HS-COMPLETED c8:69:cd:0d:21:d2
Fri Sep 27 09:12:23 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.110 c8:69:cd:0d:21:d2
Fri Sep 27 09:12:23 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.110 c8:69:cd:0d:21:d2 Home-Theater
Fri Sep 27 09:13:33 2024 daemon.notice hostapd: wl1-ap0: AP-STA-DISCONNECTED c8:69:cd:0d:21:d2
Fri Sep 27 09:13:34 2024 daemon.info hostapd: wl1-ap0: STA c8:69:cd:0d:21:d2 IEEE 802.11: disassociated
Fri Sep 27 09:13:34 2024 daemon.info hostapd: wl1-ap0: STA c8:69:cd:0d:21:d2 IEEE 802.11: authenticated
Fri Sep 27 09:13:34 2024 daemon.info hostapd: wl1-ap0: STA c8:69:cd:0d:21:d2 IEEE 802.11: associated (aid 2)
Fri Sep 27 09:13:34 2024 daemon.notice hostapd: wl1-ap0: AP-STA-CONNECTED c8:69:cd:0d:21:d2 auth_alg=open
Fri Sep 27 09:13:34 2024 daemon.info hostapd: wl1-ap0: STA c8:69:cd:0d:21:d2 WPA: pairwise key handshake completed (RSN)
Fri Sep 27 09:13:34 2024 daemon.notice hostapd: wl1-ap0: EAPOL-4WAY-HS-COMPLETED c8:69:cd:0d:21:d2
Fri Sep 27 09:13:34 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.110 c8:69:cd:0d:21:d2
Fri Sep 27 09:13:34 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.110 c8:69:cd:0d:21:d2 Home-TheaterAVM Fritzbox 4040 via Attended Sysupgrade from 23.05.03 to 23.05.05 without any problems.
Thx to all devs and supporter! 
2 Likes
Network names are not from OpenWRT. ubus call system board + sha1sum of image you flashed.....
Here you go
root@Router:~# ubus call system board
{
"kernel": "5.15.167",
"hostname": "Router",
"system": "ARMv8 Processor rev 4",
"model": "Linksys E8450 (UBI)",
"board_name": "linksys,e8450-ubi",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.5",
"revision": "r24106-10cc5fcd00",
"target": "mediatek/mt7622",
"description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
}
}
root@Router:~#
the image is from
https://downloads.openwrt.org/releases/23.05.5/targets/mediatek/mt7622/
linksys_e8450-ubi-squashfs-sysupgrade.itb 378e5642b590242330ce6cd99157077ec21a9acfe38789a1e4c1d07376d723fc 9676.3 KB Tue Sep 24 05:52:51 2024
shasum -a 256 openwrt-23.05.5-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb
378e5642b590242330ce6cd99157077ec21a9acfe38789a1e4c1d07376d723fc openwrt-23.05.5-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb
The access point names are strange as if config was copied from some fork or something.
The only nonstandard thing in my setup is that my provider is T-Mobil Internet with its CGNAT and I have applied IPv6 NAT. Everything else is vanilla OpenWRT.
uci set firewall.@zone[1].masq6="1"
uci commit firewall
service firewall restart
uci set dhcp.lan.ra_default="1"
uci commit dhcp
service odhcpd restart
uci set network.wan6.sourcefilter="0"
uci commit network
service network restart
It is rather strange, as the wifi interfaces name phy0-ap0 and so on....
search forim for help with apple acceptable settings, like it will ignore wpa1 and tkip, or 5ghz in dfs without 2.4 backup.
updated my 3 active devices via Attended Sysupgrade this was superfast and no issues.
I don't have measurements, but lately had some issues/hickups during video calls, but today none, so maybe something is better now.
I've just updated my archer A6 v3 to 23.05.5, everything seems to be normal so far.
For some weird reason the first time i tried flashing the firmware... nothing has happened after a few mins and router rebooted back into the exact state it was before flashing.
Then I tried to do it again and it worked fine that time. I don't have any idea what might have happened there...
I upgraded an x86_64 from 23.05.4 to 23.05.5 via Attended System Upgrade ( from LUCI ), with option of keeping configuration. No issues so far, but will report back if I find any. Thanks.
Note: if you are loading an additional firmware module, (such as DMC PM) via the initrd method with bootloader using a .cpio ( as detailed here Silly little i915 issue on x86 - #16 by tmn505 ) you will need to redo that after upgrade.
Linksys WRT3200ACM
Sysupgrade via LuCI
3m far away from router, 650 Mbit - 780 Mbit, 5GHz, Lenovo X1Carbon 2nd Gen., Debian.
Thanks to all Devs.
Did a great Job!
Neuro
3 Likes
What about Raspberry Pi 5 stable release???
That is out of the question for 23.05.x, for that you will have to wait for 24.xy.0 (or main snapshots until then).
3 Likes
Upgraded Raspberry Pi4 from 23.05.3. Everything works smooth as of now. Maybe slight performance boost and stability in SQM not sure but all good.
Upgraded my GL iNet-750 tonight from 23.05 to 23.05.5.
I am now getting the following error:
Error loading theme
A fallback is used since the configured theme failed to load with the error below.
Unable to compile 'themes/openwrt2020/header' as Lua template: Unable to load Lua runtime
Edit: I had to reinstall the theme and it started to work.
1 Like
That is because the theme is not included in the image you flashed. Simply reinstall the theme and it should be gone.
2 Likes
you know there are time zones?
when you posted this, for me is was already noon.
however, when I used this method to update, there was no queue at all, so maybe something got stuck
1 Like
Mid-afternoon EST: Queued...
Request in build queue position 568