It's not going to hurt to have all enabled but also not the optimized solution. I would suggested reading up on (google "RedHat RPS" for a primer) it but the TDLR: spread the IRQS evenly among the cores, RPS is the software implementation of RSS, don't bother with XPS unless you're tuning on the actual server, use taskset & napi threading.
1 Like
Try disabling disassociate on low acknowledgement in Wi-Fi settings.
Can I ask if your device is a Xiaomi?
Is it able to get again the connection?
Thanks
Device is an iPhone. It switched from 2.4G to 5G without issue. Hostapd somehow thinks that it’s still at 2.4G. iPhone is still connected and able to use the network.
1 Like
I'm seeing exactly the same on RC5 with an iPhone. In my case the device roamed from 2.4 to 5GHz:
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)
First off all my devices are installed as dumb ap's with opnsense as the router(bare metal).
When I first setup the devices vlans where created as separate vlanq devices with its designated bridge.
Now I just switched to Vlan filtering on the main BRLAN bridge. As a noob glad i have a test device as I am not the only one living in my house. Maybe that i want to feel it but everything appears to work more consistent les drops in connection etc. The reason I switched was that I saw a lot off blocking state errors in my kernel log and occasionally had the problem that my GLMT6000 needed a reboot because the internet connection was lost. The strange thing is this happens only on 1 vlan the other SSID's with its own VLAN id where still working. ( Only on the 5ghz band) Cannot say if the issues appear less or not because just switched to vlan filtering. Question if somebody knows?? Are there differences in VLAN distribution?or could it be that our device works better with a specific type of distribution?
You logs looks different from what I have encountered tho. From your logs it appears to me that transmission signals between your iPhone and GL-MT6000 likely is weak due to both devices being far apart?
Looks like your iPhone is trying to repeatedly connect to the AP but thinks that it got disconnected due to weak signal?
For my case, I think it is likely hostapd is likely confused that my iPhone is connected to both 2.4G and 5G interface at the same time (I read this is part of 802.11ax IIRC) and hostapd likely is not supporting this scenario? Just a guess. Not familiar with how hostapd works tho.
No the iPhone was within a few meters, and once the connection was established, the link-speed was somewhere >700Mbps. Below another instance of this issue, a laptop with 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)
Hmm ... looks like more bugs with hostapd? Doesn't look like it is due to the mt76 driver.
Keep an eye on the PR for the newer hostapd 17423. Maybe your issue will resolve there. I'm seeing no such log spam with rc6 (it's running pretty much perfect actually) but I don't roam between bands like that, I only have a couple IoT type devices on 2.4 right now, my main devices are on 5.1 GHz so no issue observed here.
1 Like
I'm not 'consciously' roaming by moving around the house though. In both examples, the clients were not moving and within 4 meters of the AP. The initial connection seems to go to 2.4, then the client wants to go to 5, and then the ping-ponging you see in the log happens.
After a few minutes, the connection seems to 'settle' on 5GHz with good signal strength and link speed, the clients work without issue and no more log spam is seen.
1 Like
There are two related patches
hostapd, old patch https://github.com/openwrt/openwrt/blob/6a7fa68569ac11bb2c2abb14026e8b84acd3a12f/package/network/services/hostapd/patches/050-Fix-OpenWrt-13156.patch
mt76, new patch https://github.com/openwrt/mt76/commit/5fe42ec88fd1d698c15fd8a17ef86c4842831b99
5 Likes
What is the status on getting either of those into 24.10?
1 Like
They both are in 24.10...
4 Likes
Are they in snapshot too?
Forgive me if this has already been addressed, but what's the client to client throughput this router can do over Wi-Fi under ideal conditions, e.g. in iperf3 tests? Using the latest 23.05.x or 24.10.x.
Could it be wireless network congestion in your case. Maybe there’re too many wireless network using the same frequency?
These arent ideal conditions (router pretty far from pc) but could be helpful
Download test using iperf3 1.02 Gbits/sec
Upload test using iperf3 661 Mbits/sec
1 Like
Is there any way to get mtk drivers on plain openwrt 24.10? I dont like factory image, but I hear a lot that mtk drivers are better than open source.
1 Like
Just to be clear: that's wireless device to wireless device and not device to router, right? Either way, that 600 Mbps upload is a bit disappointing, as I was getting 800-900 Mbps on my old AC AP.