I've flashed it on a couple of BT Home Hub 5A. 23 days uptime one the one I'm currently using, however on both, the ethernet ports 1 - 3 keep dropping, the lower the port number, seemingly the more frequent they drop. Port 4 and the wan port are usable for me.
1 Like
I've not noticed anything. I've got logs forwarded, and this is what I get for ports since last boot. I'll leave it up longer and have a look - today I was playing with configs and various machines were up and down.
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.522325] ath10k_pci 0000:02:00.0: pdev param 0 not supported by firmware
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.578258] br-lan: port 5(phy0-ap0) entered blocking state
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.582520] br-lan: port 5(phy0-ap0) entered disabled state
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.613630] gswip 1e108000.switch: port 4 failed to add 00:37:b7:22:80:29 vid 0 to fdb: -22
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.644000] gswip 1e108000.switch: port 2 failed to add 00:37:b7:22:80:29 vid 0 to fdb: -22
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.650984] gswip 1e108000.switch: port 0 failed to add 00:37:b7:22:80:29 vid 0 to fdb: -22
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.705667] gswip 1e108000.switch: port 1 failed to add 00:37:b7:22:80:29 vid 0 to fdb: -22
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.712683] gswip 1e108000.switch: port 4 failed to add 00:37:b7:22:80:29 vid 1 to fdb: -22
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.784087] gswip 1e108000.switch: port 2 failed to add 00:37:b7:22:80:29 vid 1 to fdb: -22
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.823916] gswip 1e108000.switch: port 0 failed to add 00:37:b7:22:80:29 vid 1 to fdb: -22
2025-03-03T12:13:11+00:00 OpenWrt kernel: [ 63.830928] gswip 1e108000.switch: port 1 failed to add 00:37:b7:22:80:29 vid 1 to fdb: -22
2025-03-03T12:13:14+00:00 OpenWrt kernel: [ 66.886554] br-lan: port 5(phy0-ap0) entered blocking state
2025-03-03T12:13:14+00:00 OpenWrt kernel: [ 66.890762] br-lan: port 5(phy0-ap0) entered forwarding state
2025-03-03T14:58:23+00:00 OpenWrt kernel: [ 1321.606285] br-lan: port 2(lan2) entered disabled state
2025-03-03T14:58:25+00:00 OpenWrt kernel: [ 1323.679225] br-lan: port 2(lan2) entered blocking state
2025-03-03T14:58:25+00:00 OpenWrt kernel: [ 1323.684434] br-lan: port 2(lan2) entered forwarding state
2025-03-03T14:58:31+00:00 OpenWrt kernel: [ 1328.876439] br-lan: port 2(lan2) entered disabled state
2025-03-03T22:02:39+00:00 OpenWrt kernel: [26778.603070] br-lan: port 2(lan2) entered blocking state
2025-03-03T22:02:39+00:00 OpenWrt kernel: [26778.608233] br-lan: port 2(lan2) entered forwarding state
2025-03-03T22:02:53+00:00 OpenWrt kernel: [26792.120677] br-lan: port 2(lan2) entered disabled state
2025-03-03T22:02:55+00:00 OpenWrt kernel: [26794.213593] br-lan: port 2(lan2) entered blocking state
2025-03-03T22:02:55+00:00 OpenWrt kernel: [26794.218802] br-lan: port 2(lan2) entered forwarding state
I had a problem with an earlier version of 24.10.0 with Avahi on WRT1900. I'm assuming it's now working well for you on the stable release?
i've not had any issues
1 Like
The 24.10.0 release notes mention "Improved support for WiFi6 (802.11ax)". I could not find more information anywhere on what exactly these improvements are.
Would someone be able to tell me / refer me to documentation on what these Wifi6 improvements are?
Thank you!
2 Likes
I don't know about specific cases - but there are many WiFi changes in https://openwrt.org/releases/24.10/changelog-24.10.0-rc1
Successful upgrade to 24.10.0 from 23.05.5 on WRT1900ACSv2. Unable to install package luci-app-samba4 secondary to size. Package sizes may have changed or perhaps the firmware image is larger. Additionally, I can't seem to get Avahi to work the same as 23.05.5.
I'm trying to use Samba4 but can't seen to make it work, do you know a good guide that I can follow?
@user34 Maybe try the kmsbd package that's what I'm using it works great.
@Christoph34 the guide is here: https://openwrt.org/docs/guide-user/services/nas/cifs.server
2 Likes
I will, thankyou
A change was made to opkg at some point so that it when it checks for available free overlay space it uses the total uncompressed data size of the package(s) rather than the compressed data size (which it used for 23.05).
The overlay file system uses compression when storing files, but opkg has no way of computing the amount of flash space actually required for the package files once they're stored in compressed form. The change means that users should never run into the situation where the overlay file system is filled while installing packages (which could and did happen before the change) but at the price of denying installation of packages that would actually comfortably fit.
If you review the situation and decide that the package should actually fit, you can force package installation. If it goes pear shaped, factory reset the device or use fail-safe mode to wipe the overlay file system (firstboot) and start over. Or use one of the custom image creation options (image builder, owut, asu, auc etc) to beuild the required packages into a custom image.
7 Likes
A better solution would be to use the firmware selector to build an image that already contains luci-app-samba4.
Migrated from Samba4 to kmsbd successfully. Thank you for this suggestion! Took me an embarrassingly long time to find the following command:
2 Likes
Comfast E-395AX no longer accessible after using sysupgrade from 23.05. Device is still working to pass packets, but can't be access via gui or ssh.... wonderful.
Something must have changed in 24.10.0 from 23.05.5 to not allow mDNS repeating between VLANs with Avahi for ESPHome. Avahi seems to be running, but I loose functionality.
Edit: Fixed. I had to reconfigure Avahi such that the allowed interfaces included the IoT interface (br-IoT) instead of the vlan bridge that included the IoT interface (br-lan3). Not sure if there was a subtle change in DSA implementation, but glad to have it working again.
4 Likes
24.10 Soft bricks TP-Link EAP615-Wall v1.
Fail - Upgrade from 23.05 keeping settings
Fail - Upgrade from 23.05 not keeping settings
Fail - recovery procedure and factory 24.10
Works - recovery procedure and factory 23.05
Unfortunately, don't have easy access to plug a console cable into.
I did notice, there was someone reporting TP Link 615 working at the start of this thread. Could there be a setting from the RC not implemented in final?
I have three EAP615's running 24.10 (upgraded from 23.05.5 => 24.10.0-rc4 => 24.10.0 without retaining settings, using vanilla sysupgrade image)
Opening the EAP615 case for console access is doable but requires quite some force.
Just installed this on a Netgear R7450 and it seems to not always boot up successfully. It will start to reboot but the power light will stay white and nothing else happens so I have to power cycle it. Out of 5 reboots it might boot 2 or 3 times successfully. I decided to try to go back to 23.05.5 and it has been fine ever since. Is there any info I can provide without opening the device up that would help find the cause of this?
1 Like
The same with zr-2660 (ramips mt7621).
Same issue with Linksys WHW03 V2 (Qualcomm IPQ4019), that said I don't know if is not booting properly or if is booting and the interfaces are down. That said I have setup watchcat to reboot the interfaces if pinging local network device (managed switch) that is always on fails 3 times on a row and full device reboot if the fails more that 5 times. This way it always get's up eventually. I have 6 nodes of WHW03 and eventualy all have this issue but it's very random when occurs. With this work around I have been able to keep version 24.10 stable on them, only use this work around since I only use them as AP's my main router is a Flint 2 running also 24.10.