I'm keen to follow the outcome of this too as I've got a couple of Raspberry Pi zero devices connected via USB to my OpenWRT router.
Not that I'm aware of. Posting your question directly in mx4xxx support thread can yield better result. OpenWrt support for Linksys MX4200
1 Like
will do.thank u 
Sysupgrade with old config preserved from 24.10.0 to 24.10.1 on two devices (Linksys E8450 (UBI) and OpenWrt One). Both devices running well.
Thank you devs!
1 Like
I updated two Zyxel WSM 20 and a Zyxel NWA50AX Pro from 23.05 to 24.10.1 and a GLinet MT6000 from an older snapshot to 24.10.1 - no problems so far
Successful upgrade on my NanoPi R3S from 24.10.0. Cheers!
2 Likes
Still no fix for the R4S not getting a LAN connection after reboot 
GL-iNET MT6000 here: upgrade from 24.10.0 went smooth just now, need to test further to determine if all is fine.
Thank you for posting this. These are the exact reasons I skim the comments for people using my device before upgrading. I'll test when I have more time on the WRT1900ACSV2. I wonder if the following is the reason:
The only person I've seen submitting bug reports has a bad habit of cursing those responding - causing their posts/accounts to be moderated.
EDIT:
Making 100% clear that I'm not referring to @Ramon - due to numerous posts from him - and him sending incoherent PMs to me - after making clear a deleted user in the past made cursing reports prior to him. I can only logically explain the behavior as intentionally disingenuous or that of a Time Traveler. He explained he genuinely feels his reputation was injured - so I publicly offer an apology and explanation for that here.
5 Likes
Fortunately, progress on fixing the 24.10 NanoPi R4S lan port regression in PR 18078 has become more constructive of late. hauke has indicated he would accept the PR if a last remaining comment is resolved.
Should that not happen, acknowledging this regression in future release notes until it is fixed, either in OpenWrt or upstream, could help reduce the temperature on the issue. It is now clear from PR 18078 that this was not a problem in 23.05, and just as clear that it is a real problem in 24.10.
Back porting the rockchip disable kernel preemption commit in 24.10 to 23.05 would also be helpful if this is never fixed. This commit not only improved VPN performance, but restored a ~40% rockchip QoS throughput deficit relative to friendlywrt. QoS (CAKE) is the NanoPi R4S raison d'être for many.
2 Likes
Hi... 24.10.1 release notes doesn't specify any security fixes, but when you check changelog there are many (CVE-2023-42667, CVE-2023-49141 and so on). These are minor fixes that are not relevant to put on release notes, or should be considered to update to 24.10.1?
1 Like
OLD router xiaomi mi mini usb2+ USB2 MT7620A 1core mips 580MHz;
16MB/128MB DDR2; WiFi 2.4Ghz 2x2 (300M) + 5Ghz 2x2 (867M); WAN 100M + LAN х2 100M
OpenWrt 24.10.1 r28597-0425664679 / LuCI (HEAD detached at 2ac26e56) branch 25.103.51521~2ac26e5
opkg update opkg install kmod-usb-net-cdc-ether usb-modeswitch
*restart, 2min waiting... Nowhere in the [Network] v [Interfaces] v [Add new interface] 
USB LTE E3372H -320 Hilink modem (the most **** version of them without custom firmwares, root, scripts, TTL fixes ...), newest firmware 10.0.3.1 (h192sp2c983), webui 10.0.3.1 (W13SP3C7702). OK on the PC with smartphone's SIM, 192.168.8.1 default webgui, green led - connected LTE, SMS ok, but in the router it did not even appear in the GUI Interfaces.
dmesg
[ 4.079122]
[ 4.079122] ehci-platform 101c0000.ehci: irq 26, io mem 0x101c0000
[ 4.095557] ehci-platform 101c0000.ehci: USB 2.0 started, EHCI 1.00
[ 4.103476] hub 1-0:1.0: USB hub found
[ 4.108525] hub 1-0:1.0: 1 port detected
[ 4.124846] ohci-platform 101c1000.ohci: Generic Platform OHCI controller
[ 4.131918] ohci-platform 101c1000.ohci: new USB bus registered, assigned bus number 2
[ 4.140317] ohci-platform 101c1000.ohci: irq 26, io mem 0x101c1000
[ 4.176844] hub 2-0:1.0: USB hub found
[ 4.181573] hub 2-0:1.0: 1 port detected
[ 4.198865] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 4.208270] init: - preinit -
[ 4.515374] usb 1-1: new high-speed USB device number 2 using ehci-platform
[ 7.250377] random: crng init done
[ 8.313618] 8021q: adding VLAN 0 to HW filter on device eth0
[ 10.096514] jffs2: notice: (459) jffs2_build_xattr_subsystem: complete building xattr subsystem, 35 of xdatum (3 unchecked, 26 orphan) and 39 of xref (13 dead, 15 orphan) found.
[ 10.114885] mount_root: switching to jffs2 overlay
[ 10.123341] overlayfs: upper fs does not support tmpfile.
[ 10.139074] urandom-seed: Seeding with /etc/urandom.seed
[ 10.268133] procd: - early -
[ 10.271457] procd: - watchdog -
[ 10.894353] procd: - watchdog -
[ 10.898826] procd: - ubus -
[ 11.058021] procd: - init -
[ 12.856887] kmodloader: loading kernel modules from /etc/modules.d/*
[ 13.576752] jitterentropy: Initialization failed with host not compliant with requirements: 9
[ 14.048041] Loading modules backported from Linux version v6.12.6-0-ge9d65b48ce1a
[ 14.055797] Backport generated by backports.git v6.1.110-1-35-g410656ef04d2
[ 14.686254] mt76x2e 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4
[ 14.692976] mt76x2e 0000:01:00.0: ASIC revision: 76120044
[ 15.401807] mt76x2e 0000:01:00.0: ROM patch build: 20141115060606a
[ 15.432566] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[ 15.438211] mt76x2e 0000:01:00.0: Build: 1
[ 15.442461] mt76x2e 0000:01:00.0: Build Time: 201607111443____
[ 15.510572] mt76x2e 0000:01:00.0: Firmware running!
[ 15.515767] mt76x2e 0000:01:00.0: registering led 'mt76-phy0'
[ 15.523776] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 15.838134] PPP generic driver version 2.4.2
[ 15.881898] NET: Registered PF_PPPOX protocol family
[ 16.023159] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
[ 16.031564] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620 detected
[ 16.040421] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 16.502510] jitterentropy: Initialization failed with host not compliant with requirements: 9
[ 17.391050] kmodloader: 1 module could not be probed
[ 17.396472] kmodloader: - jitterentropy_rng - 0
[ 62.769378] 8021q: adding VLAN 0 to HW filter on device eth0
[ 62.871528] br-lan: port 1(eth0.1) entered blocking state
[ 62.877088] br-lan: port 1(eth0.1) entered disabled state
[ 62.882732] eth0.1: entered allmulticast mode
[ 62.887200] mtk_soc_eth 10100000.ethernet eth0: entered allmulticast mode
[ 62.894558] eth0.1: entered promiscuous mode
[ 62.898954] mtk_soc_eth 10100000.ethernet eth0: entered promiscuous mode
[ 63.055644] br-lan: port 1(eth0.1) entered blocking state
[ 63.061274] br-lan: port 1(eth0.1) entered forwarding state
[ 74.482702] ieee80211 phy1: rt2800_rxiq_calibration: Warning - RXIQ calibration FAIL
[ 74.514450] br-lan: port 2(phy1-ap0) entered blocking state
[ 74.520335] br-lan: port 2(phy1-ap0) entered disabled state
[ 74.526165] rt2800_wmac 10180000.wmac phy1-ap0: entered allmulticast mode
[ 74.533575] rt2800_wmac 10180000.wmac phy1-ap0: entered promiscuous mode
[ 83.315231] ieee80211 phy1: rt2800_rxiq_calibration: Warning - RXIQ calibration FAIL
[ 83.351809] br-lan: port 2(phy1-ap0) entered blocking state
[ 83.357546] br-lan: port 2(phy1-ap0) entered forwarding state
[ 147.592279] urngd: v1.0.2 started.
[ 372.841600] usb 1-1: USB disconnect, device number 2
[ 376.004912] usb 1-1: new high-speed USB device number 3 using ehci-platform
[ 420.916573] usb 1-1: USB disconnect, device number 3
[ 421.967238] usb 1-1: new high-speed USB device number 4 using ehci-platform
root@OpenWrt:~#
[ 372.841600] usb 1-1: USB disconnect, device number 2
[ 376.004912] usb 1-1: new high-speed USB device number 3 using ehci-platform
[ 420.916573] usb 1-1: USB disconnect, device number 3
[ 421.967238] usb 1-1: new high-speed USB device number 4 using ehci-platform
[ 477.549452] usb 1-1: USB disconnect, device number 4
[ 501.098871] usb 1-1: new high-speed USB device number 5 using ehci-platform
[ 504.508730] usb 1-1: USB disconnect, device number 5
[ 505.108392] usb 1-1: new high-speed USB device number 6 using ehci-platform
lsusb
root@OpenWrt:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.6.86 ehci_hcd EHCI Host Controller
Bus 001 Device 007: ID 12d1:14db HUAWEI_MOBILE HUAWEI_MOBILE
Bus 002 Device 001: ID 1d6b:0001 Linux 6.6.86 ohci_hcd Generic Platform OHCI controller
USB LTE E3372H -320 Hilink not working!( OpenWRT 24.10.1
I have now upgraded to 24.10.1 using Attended Sysupgrade and confirm having to change back from eth4 and eth5 to usb0 and usb1 for a couple of USB connected Raspberry Pi Zero devices to continue working. Essentially reversing a configuration change I made for my br-lan device with 24.10.
Note, I had to remove all Avahi related packages before Attended Sysupgrade would work on my x86/64 APU4D4, but I just reinstalled the ones I had manually after upgrading.
1 Like
If you're remote, perhaps you could create a temporary bridge device containing both eth0 (exists on 24.10) and manually add usb0 (inexistent on 24.10) to it before upgrading, so that after upgrading to 24.10.1 things will still work? A bit risky playing around with that kinda thing from such a distance, though. I suspect that even just adding both devices to a bridge will break any current connections to it.
1 Like
Thanks for confirming the reversion. Fortunately I only have a single device attached, so in my case I know that my change will be limited to my eth0 device changing back to usb0. So I just need to make a pretty simple text substitution in /etc/config/network and then trigger a reboot.
I started out wondering if I could add my own uci-defaults script, that only gets executed once after the reflash. But then it dawned on me I don't need anything that clever - I can just add some idempotent code into /etc/rc.local, make sure its preserved across the reflash, and it will be executed at the end of every reboot.
So I think I have a plan that doesn't involve a road trip - hooray!
1 Like
Zyxel T-56 (EX5601-T0 ubootmod) updated to 24.10.1 from 24.10.0 without issues.
Updated my GL Inet AR300M16 travel router via ASU, from 23.05.
No issues.
Thanks Devs!
No Ethernet link stability issues with Zyxel WSM20 (MT7530 switch)?
Updated GL.iNet GL-MT3000 from 23.05.5 without retaining settings.
It has been running stable since a few days now.
to all OpwnWrt contributors