OpenWrt 24.10.0-rc6 - Sixth Release Candidate

Hi,

The OpenWrt community is proud to announce the sixth release candidate of the upcoming OpenWrt 24.10 stable series.
OpenWrt 24.10.0-rc6 incorporates over 5300 commits since branching the previous OpenWrt 23.05 release and has been under development for over one year.

This is just a release candidate and not the final release yet.

Download firmware images using the OpenWrt Firmware Selector:

Please test this version

This is not the final version, this is a test version. Please report problems and bugs in our issue tracker. https://github.com/openwrt/openwrt/issues
If there is already an existing ticket feel free to comment that the problem also occurs with OpenWrt 24.10.0-rc6.

Changes between OpenWrt 24.10.0-rc5 and 24.10.0-rc6

Target changes:

  • airoha: Multiple fixes
  • apm821xx: WNDAP620 + WNDAP660: Fix sysupgrade failures
  • armsr: change image names to 'combined-efi'
  • ath79: AR9344: fixes spurious reset hangs
  • ath79: meraki-mr18: fix initramfs build
  • ath79: teltonika-rut230: fix failsafe boot without SIM tray
  • ath79: zte-mf28x-common: fix initramfs execution
  • d1: Use correct module for devices with wifi
  • ipq4019: FritzBox 7530: Fix initialization of Lantiq DSL
  • ipq40xx: Fix MAC address
  • kernel: Realtek PHY improvements
  • lantiq: AVM FritzBox 7430: Add fritz_cal_extract with reverse option
  • lantiq: xrx200_legacy: disable unused PHY drivers to reduce image size
  • mediatek: Xiaomi AX3000t: fix soft brick for the rd23 model
  • mvebu: WD Cloud Mirror Gen2: Add new device
  • qualcommax: dl-wrx36: Fix 2.5G port LED-s
  • ramips: mt7621: Confiabits MT7621 v1: Add new device
  • ramips: mtk_eth_soc: reduce driver memory usage
  • realtek: Zyxel GS1900: debounce reset key
  • rockchip: disable kernel preemption to increase VPN performance

Generic changes:

  • Linux Kernel update to version 6.6.73
  • mt76: update to Git HEAD (2025-01-14)
  • lldpd: bump version to 1.0.18
  • lldpd: fix config for build without LLDP-MED
  • hostapd: backport upstream patch to fix setting BSS color
  • hostapd: fix processing mbssid config option
  • netifd: improve packet steering on ipq40xx (and possibly others)
  • wifi-scripts: add macaddr_base wifi-device option
  • wifi-scripts: add option to set per-device ifname prefix
  • wifi-scripts: allow per-IF mesh basic rate selection

For a detailed list of changes since OpenWrt 24.10.0-rc6 see the 24.10.0-rc6 changelog.

Highlights in OpenWrt 24.10:

General changes

  • TLS 1.3 support in default images
    • mbedtls was updated to version 3.6 which includes support for TLS 1.3
  • Activate POSIX Access Control Lists and file system security attributes for all file systems on devices with big flash sizes. This is needed by docker nowadays.
    • This is activated for all targets which do not have the small_flash feature flag. small_flash is set for the ath79/tiny, bcm47xx/legacy, lantiq/ase, lantiq/xrx200_legacy, lantiq/xway_legacy, ramips/mt76x8, ramips/rt288x, ramips/rt305x and ramips/rt3883 targets.
  • Activate kernel support for Multipath TCP on devices with big flash sizes.
  • Improved support for WiFi6 (802.11ax) and initial support for WiFi7 (802.11be)
    • Not many Wifi7 devices are supported by OpenWrt yet
  • Improved Link Layer Discovery Protocol (LLDP) support
  • OpenWrt 24.10 uses OPKG only, APK packages are not supported. Only main branch was changed to APK.

Many new devices added

OpenWrt 24.10 supports over 1950 devices. Support for over 100 new devices was added in addition to the device support by OpenWrt 23.05.

Target changes

  • Added d1 target for AllWinner D1 RISC-V SoC
  • Added ixp4xx target for Intel XScale IXP4xx SoCs.
  • Added loongarch64 target for SoCs with Loongson LoongArch CPUs.
  • Added starfive target for StarFive JH71x0 (7100/7110) SoCs.
  • Added stm32 target for STMicroelectronics STM32 SoCs.
  • Renamed ipq807x target to qualcommax.
  • Removed ath25 target. It supported Atheros ieee80211g devices with maximum 16MB RAM
  • Removed bcm63xx target. It supported some Broadcom DSL MIPS SoCs and was replaced by the bmips target. The Broadcom DSL itself was never supported.
  • Removed octeontx target. It supported the Octeon-TX CN80XX/CN81XX based boards
  • Removed oxnas target. It supported the PLXTECH/Oxford NAS782x/OX8xx
  • The qoriq target for the NXP QorIQ (PowerPC) SoCs is built
  • The ipq806x target for Qualcomm Atheros IPQ806X SoCs was converted to DSA
  • Added support for Airoha AN8855 DSA Switch (Xiaomi AX3000T ship both Mediatek and Airoha Switch in the same revision)

Core components update

Core components have the following versions in 24.10.0-rc6:

  • Updated toolchain:
    • musl libc 1.2.5
    • glibc 2.38
    • gcc 13.3.0
    • binutils 2.42
  • Updated Linux kernel
    • 6.6.73 for all targets
  • Network:
    • hostapd master snapshot from September 2024, dnsmasq 2.90, dropbear 2024.86
    • cfg80211/mac80211 from kernel 6.12.6

Upgrading to 24.10

Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.

  • Sysupgrade from 22.03 to 24.10 is not officially supported.

  • 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.
    ''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''

  • User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.

  • Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.

  • Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.

Known issues


Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.0-rc6

In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.0-rc6#known_issues

For a detailed list of all changes since 24.10.0-rc5, refer to
https://openwrt.org/releases/24.10/changelog-24.10.0-rc6

To download the 24.10.0-rc6 images, navigate to:
https://downloads.openwrt.org/releases/24.10.0-rc6/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=24.10.0-rc6

As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.

Have fun!

The OpenWrt Community


To stay informed of new OpenWrt releases and security advisories, there
are new channels available:

21 Likes

A few issues with upgrades you may run into:

  1. It looks like at least x86 and ath79 haven't been picked up by ASU server, so Firmware Selector, owut and LuCI app are failing to build those targets (error is Unsupported profile: ...). Reported to aparcar.

  2. The LuCI Attended Sysupgrade app has a bug, so it's not picking up the latest 24.10 rc. PR submitted an hour ago. LuCI app users will need to either use Firmware Selector or owut until the package gets updated.

8 Likes

Flashed on my GL-MT6000. Lots of added packages etc, fantastic so far.

A few comments prior to final release:

  • daemon.err hostapd: nl80211: kernel reports: integer out of range - log spam is fixed! I see 7673390 . Thanks, wifi is working awesome in general too.
  • Packet Steering: Enabled (All CPUs) option 2 is gone from LuCI from rc5 to rc6. Only Enabled or Disabled are available now. Performance with enabled seems good, but anyone know if this was intentional? Might have been prior to d889c27. Coded as: o.value('2',_('Enabled (all CPUs)')); does not show up.
  • Rockchip: please backport 17683 to 24.10. NanoPi targets really need the affinity tuning for better performance due to hybrid cores.
  • Ksmbd: Please backport 225519 to 24.10. Better config settings for better ksmbd performance.

Thanks to all the devs!

5 Likes

I see a lot of hostapd logentries on my GL-MT6000 on both RC5 and RC6. It seems to happen when devices roam from 2.4 to 5GHz bands. Initial wireless connection is slow to establish, but once connected there are no issues.

This is from an iPhone:

Thu Jan 23 01:28:10 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:28:10 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:28:18 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
Thu Jan 23 01:30:01 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:32:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:32:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:32:19 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:32:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:32:19 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:32:19 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:32:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Thu Jan 23 01:32:20 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 01:34:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:34:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:34:19 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:34:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:34:19 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:34:19 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:34:19 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Thu Jan 23 01:34:20 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 01:36:00 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:00 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:00 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:00 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:00 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:00 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:00 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Thu Jan 23 01:36:01 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 01:36:02 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:02 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:02 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:02 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:02 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:07 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:07 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:07 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:07 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:15 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:15 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:15 2025 daemon.notice hostapd: phy1-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:15 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:15 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:15 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:23 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:23 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:23 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:23 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:30 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:30 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:30 2025 daemon.notice hostapd: phy1-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:30 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:30 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:30 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:38 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:38 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:38 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:38 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:45 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 01:36:45 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 01:36:45 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 01:36:45 2025 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 01:36:45 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 01:36:45 2025 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 01:37:15 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

And an Intel AC adapter:

Thu Jan 23 12:11:17 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:11:17 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 2)
Thu Jan 23 12:11:17 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 12:11:17 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 12:11:17 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:17 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:13:17 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 12:13:17 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:17 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:26 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:13:26 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 12:13:26 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:26 2025 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 12:13:26 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 12:13:26 2025 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:13:56 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 12:14:23 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:14:23 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 2)
Thu Jan 23 12:14:23 2025 daemon.notice hostapd: phy1-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 12:14:23 2025 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:14:25 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 12:14:25 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 12:14:25 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:14:53 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 23 12:15:09 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 23 12:15:09 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Thu Jan 23 12:15:09 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 23 12:15:09 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:15:09 2025 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 23 12:15:09 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 23 12:15:09 2025 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 23 12:15:39 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

I come from a snapshot image built around May 2024, that did not give any of these entries. For reference my /etc/config/wireless:

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/soc/18000000.wifi'
	option country 'NL'
	option htmode 'HE20'
	option band '2g'
	option channel '1'

config wifi-iface 'wifinet0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'redacted'
	option encryption 'psk2+ccmp'
	option key 'redacted'
	option ieee80211w '1'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'platform/soc/18000000.wifi+1'
	option country 'NL'
	option htmode 'HE80'
	option band '5g'
	option channel '36'

config wifi-iface 'wifinet1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid 'redacted'
	option encryption 'psk2+ccmp'
	option key 'redacted'
	option ieee80211w '1'

Yes there are generally more log entries with the new hostapd. There is a newer hostapd build I think on snapshots but held back from 24.10 maybe try that see if it's better. Wifi is basically flawless for me right now but I'm not roaming back/forth between 2.4 and 5.1 GHz bands like you are.

I do get more of these which is new, need to look into it:

Thu Jan 23 21:41:48 2025 daemon.warn odhcpd[2052]: No default route present, overriding ra_lifetime to 0!
Thu Jan 23 21:46:02 2025 daemon.warn odhcpd[2052]: No default route present, overriding ra_lifetime to 0!
Thu Jan 23 21:50:31 2025 daemon.warn odhcpd[2052]: No default route present, overriding ra_lifetime to 0!
Thu Jan 23 21:57:23 2025 daemon.warn odhcpd[2052]: No default route present, overriding ra_lifetime to 0!
Thu Jan 23 22:03:10 2025 daemon.warn odhcpd[2052]: No default route present, overriding ra_lifetime to 0!

I’ve also noticed this same issue. It happens on all the openWRT firmware, I flashed FriendlyWRT and didn’t encounter the issue once.

Dynalink DL-WRX36
Smooth sailing using owut to sysupgrade install 24.10.0-rc6 :rocket:

Only single syslog/kernel error I'm seeing is:

kern.info kernel: [   11.112069] jitterentropy: Initialization failed with host not compliant with requirements: 9

EDIT the log entry occurs randomly, subsequent reboot(s) it disappears

BPI R4 and MT3000 do not seem complete either, owut fails for both:

Build failed in   0s total =   0s in queue +   0s to build:
ERROR: Build failed with status 400
The above errors are often due to the upgrade server lagging behind the
build server, first suggestion is to wait a while and try again.

Redmi AX6s upgraded ok.

2 Likes

Owut gives me error 400 while trying on Openwrt One.

1 Like

Xiaomi AX3200 updated without problems.

BTW, are you going to remove that warning about incompatible AX3200 flash layout? It should be easy to detect whether layout was updated or not.

x86 updated without hickups too.

Both Xiaomi AX3600 and TP-Link Archer C50v6 upgrade via owut no problems. But getting a 400 error with the D-Link DIR-853-R1. All three routers were already running RC5

Status:   Unsupported profile: dlink_dir-853-r1

ERROR: Build failed with status 400
The above errors are often due to the upgrade server lagging behind the
build server, first suggestion is to wait a while and try again.

UPDATE: Started working, update went fine without issues.

1 Like

Same^ with GL-MT6000, attempted custom build with firmware selector,
result = "Unsupported profile: glinet_gl-mt6000".

1 Like

Linksys E8450 UBI: upgraded successfully, and it came up correctly.

Netgear WAX202: "unsupported profile" EDIT: also successful (as a WDS repeater).

1 Like

just to report (I know it will be restored weather permitting):

Zyxel LTE5398-M904

Unsupported profile: zyxel_lte5398-m904
already solved... really good

OpenWrt 24.10.0-rc6 r28388-58d0057481 / LuCI openwrt-24.10 branch 25.021.30718~36b6107

successfully used owut to upgrade Mercusys MR90X.

Xiaomi AX3000T, internet does't work.

Upgrade via luci

EDIT 1:

My last installed version: OpenWrt SNAPSHOT r0-4e75b1d / LuCI Master 24.360.56502~2da1efb (everything works)

Which AX3000T model, did you upgrade without saving settings?

@hauke Thanks for OpenWRT team efforts

I opened ticket for this issue on github .... This issue reported manytimes but not solved until to now .. looking ahead for solution

This issue on all versions not solved until to now .. OpenWRT Snapshot , 24.10.0-rc2 , 24.10.0-rc3 , 24.10.0-rc4 , 24.10.0-rc5 ,24.10.0-rc6

Issue :
There is speeds limitations due to OpenWRT WIFI packages doesn't support devices that has Qualcomm WCN6856 Wi-Fi Driver

On My Laptop (Alienware AMD 19) : 60mb/s
WIFI- 160mhz (Qualcomm WCN6856 Wi-Fi Driver)

Image

On My Phone Samsung : 400 mb/s and other laptops has not have Qualcomm WiFi

Image

Laptop WIFI Information

Qualcomm WCN6856 Wi-Fi Driver

Image

I installed the Latest driver for WIFI on my computer but no improvement

Note: On BPI-R4 System that developed by BPI-R4 Company , I'm getting full speeds on WIFI for all devices ....

:100: Solution shared by OpenWRT members :

Image

2 Likes

owut on both BPI R4 and mt3000 got both upgraded smoothly now.