As you can see from the new packages, there are FIRMWARE packages, perhaps the issue is with them.
I donāt see this issue on my end. No problem with my Intel AX201 card (2402/2402 (Mbps)) or Pixel 8 but I'll keep an eye out for it. My current 24.10.3 build is from yesterday and uptime is only ~22h.
With this equipment, do you connect exclusively to 2.4G?
I look forward to your reports.
You mean you did a package upgrade after upgrading to 24.10.3? Thatās generally discouraged.
What are your wireless settings? What logs do you see when this is happening? What if you disable irqbalance (I donāt use it myself).
My router has been perfectly stable on 24.10.3. Only a few 2.4G clients using N mode, Channel 11, 20 MHz.
I compiled the firmware using ASU. I know it's not recommended to update one package at a time, and I wouldn't attempt to manually update dozens of packages either. So, the first firmware, 24.10.3, works with these settings, but the same firmware, with the updates released yesterday, doesn't. The same applies to yesterday's snapshot. I'll try updating again this evening to the version compiled yesterday and try your suggestion. The only thing that changed during the update was deleting the "syslog-ng" package, as it had disappeared. But I don't think the logging package is the cause of the WiFi glitches.
In total, my version received 58 updates, but most of them were language packs, but there were also quite a few system updates.
I also mentioned that when upgrading from version 24.10.2 and 24.10.3 to a snapshot and back, with the settings preserved, the WAN doesn't work over IPv4. It seems to work over IPv6, at least it receives addresses. I also read in a test thread about this router that someone had similar WiFi issues, but they had their own drivers and their own edits. He discovered a conflict with the "bridger" package, and after removing it, everything worked fine. That's also worth trying.
So there was no issue with updating to standard 24.10.3?
Everything was working fine until yesterday's updates. So, if you install the very first version from the website and add your own packages, everything will be fine, but if you compile it with your own packages right now, things might not work as well.
Or, when adding the packages you need, you'll end up with a new version that conflicts... You need to try. Make backups first so you can roll back to a stable version))).
Is your MT6000 an AP? Do you even have bridger installed? It's intended for dumb APs, generally. You mention WAN not working, so I'm assuming yours is also a router.
My experience may be different since I always create a new imagebuilder build with all my settings embedded via files and uci-defaults and run a sysupgrade -n whenever I upgrade. Nice and clean for me.
A router with a single network and fast roaming settings for 2.4G and 5G. I save and restore the settings using standard Luci tools.
Basically, it's not a settings issue. I flashed the image I built yesterday without saving the settings and couldn't access the router at all. Only the IPv6 address is displayed, no IPv4. When manually entering 192.168.1.10 and 255.255.255.0, I can access the router interface via 192.168.1.1. The internet connection is also almost non-functional. I don't add or change any settings during the build; everything is as is by default. I only add packets, and that's how it works. Just in case, I rebuilt the image today using ASU 24.10.3, but nothing changed. It doesn't work. The packet list is the same. The build from September 22, 2025, works as usual. If you have the time and inclination, build it now and see how it goes with your configuration.
Does that suggest dnsmasq is failing to startup and serve DHCPv4? System logs would be helpful when it's in that state.
My package list is relatively modest:
bind-dig
htop
luci-ssl
tcpdump-mini
diffutils
nano-full
curl
mtr
luci-app-adblock
luci-app-sqm
What packages do you add beyond the base install?
I have a lot more))). A complete list of all packages from the firmware.
Summary
adblock-fast
attendedsysupgrade-common
attr
avahi-dbus-daemon
base-files
block-mount
bridger
busybox
ca-bundle
cgi-io
coreutils
coreutils-sort
curl
dawn
dbus
dnsmasq-full
dropbear
e2fsprogs
eip197-mini-firmware
f2fsck
fail2ban
fdisk
firewall4
fitblk
fstools
fwtool
gawk
getrandom
glib2
grep
hostapd-common
https-dns-proxy
ip-full
iptables-mod-ipopt
iptables-zz-legacy
irqbalance
iw
iwinfo
jansson4
jshn
jsonfilter
kernel
kmod-asn1-decoder
kmod-cfg80211
kmod-crypto-acompress
kmod-crypto-aead
kmod-crypto-authenc
kmod-crypto-ccm
kmod-crypto-cmac
kmod-crypto-crc32c
kmod-crypto-ctr
kmod-crypto-des
kmod-crypto-ecb
kmod-crypto-gcm
kmod-crypto-geniv
kmod-crypto-gf128
kmod-crypto-ghash
kmod-crypto-hash
kmod-crypto-hmac
kmod-crypto-hw-safexcel
kmod-crypto-kpp
kmod-crypto-lib-chacha20
kmod-crypto-lib-chacha20poly1305
kmod-crypto-lib-curve25519
kmod-crypto-lib-poly1305
kmod-crypto-manager
kmod-crypto-md5
kmod-crypto-null
kmod-crypto-rng
kmod-crypto-seqiv
kmod-crypto-sha1
kmod-crypto-sha256
kmod-crypto-sha3
kmod-crypto-sha512
kmod-fs-exfat
kmod-fs-ext4
kmod-fs-ksmbd
kmod-fs-netfs
kmod-fs-ntfs3
kmod-fs-smbfs-common
kmod-gpio-button-hotplug
kmod-gre
kmod-gre6
kmod-hwmon-core
kmod-ifb
kmod-ip6-tunnel
kmod-ipt-core
kmod-ipt-ipopt
kmod-iptunnel
kmod-iptunnel6
kmod-leds-gpio
kmod-leds-ws2812b
kmod-lib-crc-ccitt
kmod-lib-crc16
kmod-lib-crc32c
kmod-lib-lzo
kmod-lib-textsearch
kmod-libphy
kmod-mac80211
kmod-mt76-connac
kmod-mt76-core
kmod-mt7915e
kmod-mt7986-firmware
kmod-nf-conntrack
kmod-nf-conntrack-netlink
kmod-nf-conntrack6
kmod-nf-flow
kmod-nf-ipt
kmod-nf-log
kmod-nf-log6
kmod-nf-nat
kmod-nf-nathelper-extra
kmod-nf-reject
kmod-nf-reject6
kmod-nfnetlink
kmod-nft-bridge
kmod-nft-core
kmod-nft-fib
kmod-nft-nat
kmod-nft-netdev
kmod-nft-offload
kmod-nls-base
kmod-nls-ucs2-utils
kmod-nls-utf8
kmod-oid-registry
kmod-phy-aquantia
kmod-ppp
kmod-pppoe
kmod-pppox
kmod-sched-act-vlan
kmod-sched-bpf
kmod-sched-cake
kmod-sched-core
kmod-sched-flower
kmod-scsi-core
kmod-slhc
kmod-tcp-bbr
kmod-thermal
kmod-tun
kmod-udptunnel4
kmod-udptunnel6
kmod-usb-core
kmod-usb-storage
kmod-usb-storage-uas
kmod-usb-xhci-hcd
kmod-usb-xhci-mtk
kmod-usb3
kmod-wireguard
ksmbd-server
libatomic1
libattr
libavahi-client
libavahi-dbus-support
libblkid1
libblobmsg-json20240329
libbpf1
libbz2-1.0
libc
libcap
libcap-ng
libcares
libcomerr0
libcurl4
libdaemon
libdbi
libdbus
libe2p2
libelf1
libev
libexpat
libext2fs2
libf2fs6
libfdisk1
libffi
libgcc1
libgcrypt
libgmp10
libgnutls
libgpg-error
libip4tc2
libip6tc2
libiptext0
libiptext6-0
libiwinfo-data
libiwinfo20230701
libjson-c5
libjson-script20240329
liblua5.1.5
liblucihttp-lua
liblucihttp-ucode
liblucihttp0
liblz4-1
liblzo2
libmbedtls21
libmnl0
libncurses6
libnetfilter-conntrack3
libnettle8
libnfnetlink0
libnftnl11
libnghttp2-14
libnl-core200
libnl-genl200
libnl-tiny1
libopenssl3
libpam
libpcre2
libpopt0
libpthread
libpython3-3.11
libreadline8
librt
libsmartcols1
libsqlite3-0
libss2
libtasn1
libtirpc
libubox20240329
libubus-lua
libubus20250102
libuci20250120
libuclient20201210
libucode20230711
libudebug
liburing
libustream-mbedtls20201210
libuuid1
libuv1
libwebsockets-full
libwolfssl5.7.6.e624513f
libxtables12
lua
luci
luci-app-adblock-fast
luci-app-attendedsysupgrade
luci-app-dawn
luci-app-firewall
luci-app-https-dns-proxy
luci-app-irqbalance
luci-app-ksmbd
luci-app-openvpn
luci-app-package-manager
luci-app-sqm
luci-app-ttyd
luci-app-watchcat
luci-base
luci-compat
luci-i18n-adblock-fast-ru
luci-i18n-adblock-fast-uk
luci-i18n-attendedsysupgrade-ru
luci-i18n-attendedsysupgrade-uk
luci-i18n-base-ru
luci-i18n-base-uk
luci-i18n-dashboard-ru
luci-i18n-dashboard-uk
luci-i18n-firewall-ru
luci-i18n-firewall-uk
luci-i18n-https-dns-proxy-ru
luci-i18n-https-dns-proxy-uk
luci-i18n-irqbalance-ru
luci-i18n-irqbalance-uk
luci-i18n-ksmbd-ru
luci-i18n-ksmbd-uk
luci-i18n-openvpn-ru
luci-i18n-openvpn-uk
luci-i18n-package-manager-ru
luci-i18n-package-manager-uk
luci-i18n-sqm-ru
luci-i18n-sqm-uk
luci-i18n-ttyd-ru
luci-i18n-ttyd-uk
luci-i18n-watchcat-ru
luci-i18n-watchcat-uk
luci-lib-base
luci-lib-ip
luci-lib-jsonc
luci-lib-nixio
luci-lib-uqr
luci-light
luci-lua-runtime
luci-mod-admin-full
luci-mod-dashboard
luci-mod-network
luci-mod-status
luci-mod-system
luci-proto-ipv6
luci-proto-ppp
luci-proto-wireguard
luci-ssl
luci-theme-bootstrap
mkf2fs
mt7986-wo-firmware
mtd
nano
netifd
nftables-json
odhcp6c
odhcpd-ipv6only
openvpn-openssl
openwrt-keyring
opkg
ppp
ppp-mod-pppoe
procd
procd-seccomp
procd-ujail
px5g-mbedtls
python3-base
python3-ctypes
python3-distutils
python3-email
python3-light
python3-logging
python3-pkg-resources
python3-sqlite3
python3-urllib
resolveip
rpcd
rpcd-mod-file
rpcd-mod-iwinfo
rpcd-mod-luci
rpcd-mod-rpcsys
rpcd-mod-rrdns
rpcd-mod-ucode
sed
sqm-scripts
syslog-ng
tc-tiny
terminfo
ttyd
ubi-utils
uboot-envtools
ubox
ubus
ubusd
uci
uclient-fetch
ucode
ucode-mod-digest
ucode-mod-fs
ucode-mod-html
ucode-mod-lua
ucode-mod-math
ucode-mod-nl80211
ucode-mod-rtnl
ucode-mod-ubus
ucode-mod-uci
ucode-mod-uloop
uhttpd
uhttpd-mod-ubus
umdns
urandom-seed
urngd
usign
watchcat
wifi-scripts
wireguard-tools
wireless-regdb
wpad-wolfssl
wsdd2
xtables-legacy
zlib
I can't check right now. It's evening, the family is online and watching TV. They won't understand))).
If I manually enter IPv4 in the network card settings, I can access the router. It's not distributing DHCP. I haven't figured out the exact details. It's evening, the family, watching TV))).
I updated the Snapshot today. It updated a lot of packages again, and everything started working as before. Things are getting more and more interesting.
The issue has been found and resolved.
When uninstalling the "syslog-ng" package via Luci, the dependent packages "glib2" and "libdbi" are also uninstalled, resulting in a broken internet connection and no log output. DHCP over IPv4 was restored after the package update. Yesterday, 58 packages were updated and didn't work, but today, 59 packages have already been updated. I didn't check for package errors because I don't have time. Moreover, today's snapshot automatically pulled in "glib2" and "libdbi," unlike the stable 24.10.3. It seems the dependencies in the .apk are much better built than in the .ipk.
Are you updating packages after install of 24.10.3? This is really discouraged for release builds. Sometimes it works sometimes it doesnāt.
Been running 23.10.3 with lots of added packages and configs here, has been flawless for me, but I donāt update any built-in pkgs as per this best practice.
Planning to go back to snapshots this weekend though because I miss bleeding edge.
Mostly 5GHz but I do have some 2.4GHz clients as well. Iāll take a look at 2.4GHz tomorrow.
This has reached an all time low on Amazon now at £103.99
Has anyone been able to test 5 GHz 4x4 throughput on last SNAPSHOT releases? I am seeing odd behaviour (doesn't always happen, but it has been recurring on my case)⦠and all rest of my 2x2 devices behave fine⦠weird
For example my TX gets crippled to 36 Mbps ..
Quite asymmetric, RX is at 4x4 1441 Mbps, but TX is at 1 @ 36 Mbps.
inactive time: 0 ms
rx bytes: 2695999
rx packets: 16463
tx bytes: 269728
tx packets: 1181
tx retries: 246
tx failed: 259
rx drop misc: 591
signal: -56 [-56, -64, -63, -68] dBm
signal avg: -56 [-57, -64, -62, -68] dBm
Toffset: 18446744073663827123 us
tx bitrate: 36.0 MBit/s 80MHz HE-MCS 0 HE-NSS 1 HE-GI 0 HE-DCM 0
tx duration: 302073 us
rx bitrate: 1441.3 MBit/s 80MHz HE-MCS 7 HE-NSS 4 HE-GI 0 HE-DCM 0
rx duration: 602848 us
last ack signal:-57 dBm
avg ack signal: -56 dBm
airtime weight: 256
expected throughput: 31.578Mbps
mesh llid: 0
mesh plid: 0
mesh plink: ESTAB
mesh airtime link metric: 235
mesh connected to gate: no
mesh connected to auth server: no
mesh local PS mode: ACTIVE
mesh peer PS mode: ACTIVE
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: yes
TDLS peer: no
DTIM period: 2
beacon interval:100
connected time: 315 seconds
associated at [boottime]: 62.282s
associated at: 1760845581312 ms
current time: 1760845855579 ms
UPDATE:
Loading an old SNAPSHOT gives proper link TX in 4x4⦠every time⦠no hiccup or crippling
Station ... (on phy1-mesh0)
inactive time: 0 ms
rx bytes: 277028637
rx packets: 278762
tx bytes: 1360454489
tx packets: 982124
tx retries: 64184
tx failed: 64184
rx drop misc: 15851
signal: -57 [-61, -65, -60, -67] dBm
signal avg: -56 [-60, -64, -59, -66] dBm
Toffset: 18446744070150078475 us
tx bitrate: 1441.3 MBit/s 80MHz HE-MCS 7 HE-
NSS 4 HE-GI 0 HE-DCM 0
tx duration: 19180575 us
rx bitrate: 1441.3 MBit/s 80MHz HE-MCS 7 HE-
NSS 4 HE-GI 0 HE-DCM 0
rx duration: 5615442 us
last ack signal:-57 dBm
avg ack signal: -56 dBm
airtime weight: 256
mesh llid: 0
mesh plid: 0
mesh plink: ESTAB
mesh airtime link metric: 6
mesh connected to gate: no
mesh connected to auth server: no
mesh local PS mode: ACTIVE
mesh peer PS mode: ACTIVE
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: yes
TDLS peer: no
DTIM period: 2
beacon interval:100
connected time: 513 seconds
associated at [boottime]: 20758.593s
associated at: 1760869544203 ms
current time: 1760870056805 ms
EDIT: My problems here also go away if I force the radio to 80 MHzā¦. ummmm
Maybe.
I'm on Windows 11 and have been seeing this:
Receive rate (Mbps) : 1729
Transmit rate (Mbps) : 29
Where are you getting your output from? Is this from the router? If yes, what is the command?
Anyone having wireless issues with 24.10.3? Iāve been running 24.10.2 flawlessly for months. I upgraded all three of my devices to 24.10..3 and I noticed some wireless connection problems.
I didnāt have time to t-shoot (but I still have logs captured). I just rolled back to 24.10.2 and things were stable again. We were watching the Blue Jays vs Mariners game and couldnāt be interrupted.
Not to sound any alarm bells, Iām just curious if anyone else had some intermittent connection issues with 24.10.3