I am, @egress, but my wan is 300/150,
so I wouldn't really know.
Major problems with this rc on Linksys E7350
Image built from Firmware Selector
Issues:
<issue resolved, deleted>
WAN autonegotiates to 100M speed at boot instead of 1000M
- Checked wiring, not the issue, was able to push 1.1Gbps over the same wire with other equipment
- unplugging and re-plugging causes 1000M autonegotiation
Can login to LuCI but LuCI status page is broken (won't load) and LuCI crashes at 1.15% each time when trying to upload a new firmware image.
Thanks for the new release to all devs and testers!
Upgraded a pair of devices:
Buffalo WZR-HP-AG300H
Netgear WAX206
So far just one (arguably cosmetic?) regression compared to 23.05.5 that I noticed on both of these.
Interestingly this is something I had seen in the past in a major release before 23 - can't remember/find the post/github any more unfortunately:
On a mesh wireless interface, which is configured for sae encryption, iwinfo (and, so, Luci UI) show it as having no encryption:
/etc/config/wireless:
config wifi-iface 'wifinet3'
option device 'radio0'
option mode 'mesh'
option encryption 'sae'
option mesh_id ...
option mesh_fwding '1'
option mesh_rssi_threshold '0'
option ifname 'wl-.....'
option key '...'
option network 'mesh'
However:
# iwinfo
...
wl-..... ESSID: "..."
Access Point: xx:xx:xx:xx:xx:xx
Mode: Mesh Point Channel: 1 (2.412 GHz) HT Mode: HT20
Center Channel 1: 1 2: unknown
Tx-Power: 28 dBm Link Quality: 59/70
Signal: -51 dBm Noise: -91 dBm
Bit Rate: 130.0 MBit/s
Encryption: none
Type: nl80211 HW Mode(s): 802.11b/g/n
Hardware: embedded [MediaTek MT7622]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: wl0
Edit: Found the github issue.
What's RPS 128 and Packet Steering (all CPUs) is the default packet steering option with the MT6000 and OpenWrt?
I'm using 24.10.0-rc5 (compiled locally) on a NanoPi R5C and a TP-Link EAP615, but while doing an opkg update I noticed that all the feeds in distfeeds.conf are still pointing to https://downloads.openwrt.org/releases/24.10.0-rc2/ causing some errors in the update.
After manually changing the feeds to https://downloads.openwrt.org/releases/24.10.0-rc5/ opkg is working normally again.
Will it finally have a native EIP93 support for MT7621 users?
Hello,
question to this: " There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration."
Does that mean, upgrade without the former configuration first and restore the config after successful upgrade via luci might be possible?
thanks for any hint of that topic!
Andy
No.
You upgrade not keeping config,
and you setup from scratch.
You can offc. keep a backup as an aid to review your old setup,
but you don't restore config.
You could selectively restore parts of the config (parts not relevant to dsa),
but I would advise against if you are not sure what/why are you doing,
and on a soho setup it's not too big of a job to setup from scratch anyway.
You can use hnymans trick: Build for Netgear R7800 - #3900 by hnyman
So you only have to rebuild your network, system and sqm config, which could be as easy as copying the relevant parts from your old config over to the new config
I did this recently and it works good:
3 Likes
Hi,
I reckon it would be ideal however I refrained to do this because my setup isn't on 192.168.1.0/24. My fear is I lost all connectivity to LAN and WAN doing that method and I had to connect directly into the router with a random laptop to fix config files. What do you think? Will I loose connectivity?
What I do instead is to build a custom image to flash in which I incorporate the latest config that the GUI generated. You know, the backup-OpenWrt-2025-01-08.tar.gz file and I use this script to generate the file for sysupgrade CLI:
#/bin/bash
VERSION="24.10.0-rc5"
ARCHIVE="openwrt-imagebuilder-$VERSION-octeon-generic.Linux-x86_64.tar.zst"
UPDATE="openwrt-$VERSION-octeon-generic-ubnt_edgerouter-lite-squashfs-sysupgrade.tar"
wget https://downloads.openwrt.org/releases/$VERSION/targets/octeon/generic/$ARCHIVE || exit 1
tar --zstd -xvf $ARCHIVE || exit 2
cd openwrt-imagebuilder-$VERSION-octeon-generic.Linux-x86_64
rm -rfv files
mkdir files
cd files/
tar zxvf /tmp/backup-OpenWrt-*.tar.gz || exit 3
cd ..
make image PROFILE="ubnt_edgerouter-lite" PACKAGES="mc diffutils lsblk libgcc libustream-mbedtls nftables luci uhttpd kmod-fs-vfat dosfstools block-mount" FILES="files" || exit 4
cp -v bin/targets/octeon/generic/*.tar /tmp/ || exit 5
make clean
rm -v /tmp/backup-OpenWrt-*.tar.gz
cd ..
scp -O /tmp/$UPDATE root@192.168.144.11:/tmp/$UPDATE
exit 0
Any thoughts?
Yes, it seems so.
kmod-crypto-hw-eip93
mtk-eip93 1e004000.crypto: EIP93 Crypto Engine Initialized.
Yay finally!
I do not think so, as you rename the network (and system file) a new will be generated with 192.168.1.0 network , I had no problem to connect again and copy some config from the old network.swconfig to the new network and from old system.swconfig to new system (time zone etc) so I was up and running with my new config in minutes.
But I cannot guarantee anything 
I just hope it will not be dropped as it was in 23.05 
Hi,
Thanks for the details.
I've changed my script to reflect your suggestions and will give it a try.
#/bin/bash
VERSION="24.10.0-rc5"
ARCHIVE="openwrt-imagebuilder-$VERSION-octeon-generic.Linux-x86_64.tar.zst"
UPDATE="openwrt-$VERSION-octeon-generic-ubnt_edgerouter-lite-squashfs-sysupgrade.tar"
wget https://downloads.openwrt.org/releases/$VERSION/targets/octeon/generic/$ARCHIVE || exit 1
tar --zstd -xvf $ARCHIVE || exit 2
cd openwrt-imagebuilder-$VERSION-octeon-generic.Linux-x86_64
rm -rfv files
mkdir files
cd files/
tar zxvf /tmp/backup-OpenWrt-*.tar.gz || exit 3
mv -f etc/config/system etc/config/system.swconfig
mv -f etc/config/network etc/config/network.swconfig
cd ..
make image PROFILE="ubnt_edgerouter-lite" PACKAGES="mc diffutils lsblk libgcc libustream-mbedtls nftables luci uhttpd kmod-fs-vfat dosfstools block-mount" FILES="files" || exit 4
cp -v bin/targets/octeon/generic/*.tar /tmp/ || exit 5
make clean
rm -v /tmp/backup-OpenWrt-*.tar.gz
cd ..
scp -O /tmp/$UPDATE root@192.168.167.11:/tmp/$UPDATE
exit 0
What about the other config files?
Only network and sqm have relation to DSA and system to the compat version so those are the only 3 that should be renamed before upgrading with keeping settings so the other settings should be fine and can be kept
Note those are the instructions from @hnyman who is the leading authority in these matters
2 Likes
It naturally depends on other packages that may refer to wan/lan interfaces by name in the config. (e.g. old "eth0.2" vs. new "wan")
(Above selection is enough for packages in my own builds.)
And compat version plays role only when there is abnormal change for that router.
2 Likes
1 Like
Hi to all, I'd update a Netscape WAC-104 (R6220 clone) working as AP to rc5, building from firmware-selector. Sysupgraded from 23.05. Packages installed "Wifischedule" and "Usteer" (including luci-app interfaces). Till now everything is working fine, without showing the wifi slowness recorded with rc4.
Linksys EA7500 upgrade from 23.05.05 to 24.10 RC5 went fine, didn't have to reset config, etc.
A big benefit is 160Mhz wide now seems to work properly on the 5Ghz band.