hmm i used to use Disassociate on Low Ack, than decided to stop using it, as i had some clients dropping out, but not stalling the network...
Yes, the point of the option is that clients that no longer respond to ACK (Acknowledgment) frames because they are either out of range or in a deep sleep are disconnected.
I have activated the option and have never had any problems with it.
The option only comes into play anyway when the connection is very bad or the client has a strange deep sleep / power save behavior.
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Fri Apr 29, 2022 10:43 Post subject:
ho1Aetoo wrote:
Alozaros wrote:
hmm i used to use Disassociate on Low Ack, than decided to stop using it, as i had some clients dropping out, but not stalling the network...
Yes, the point of the option is that clients that no longer respond to ACK (Acknowledgment) frames because they are either out of range or in a deep sleep are disconnected.
I have activated the option and have never had any problems with it.
The option only comes into play anyway when the connection is very bad or the client has a strange deep sleep / power save behavior.
yep...you are absolutely correct, some clients have some crap power save mode/sleep..and this contributes to bad network behaviour and frequent disconnects...so fiddling with ack time may help...
as well i do have this line in "hostapd" to help AP with inactivity...
ap_max_inactivity=600 or 900 as a value as some clients are picky...
the other WiFi stalling issue i had (on my 2,4Ghz) ages ago, was while using N-only, where some clients with draft N or B,G mode ware causing a stall, so using Mixed mode was the solution...
or using N,G mode with fixed rates
basic_rates=60
supported_rates=60 90 120 180 240 360 480 540
i guess same will apply for 5Ghz Mixed mode or AC/N as a best solution to clients rates incompatibilities...where using a proper channel is also a vital... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Updated the OP again, as we just had another repeat of the issue...
dmesg showing these:
Code:
[684359.362034] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684359.364235] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684359.369735] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684359.377414] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684359.384238] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 59 tid 0
[684489.522519] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.522553] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.528715] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.535924] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.543366] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.550593] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684489.557868] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 58 tid 0
[684539.915415] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.915449] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.921594] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.928897] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.936193] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 0
[684539.943474] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.950816] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 0
[684539.959666] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 3
[684539.966345] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 0
[684539.972638] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 61 tid 0
Here's the summary of what I've changed based on the conversation:
- Disassoc Low Ack is enabled on both 2.4 and 5GHz
- 5GHz's width is set to VHT80
- Sensitivity Range is set to 1350 on both 2.5 and 5GHz
- 2.4GHz's BI is lowered to 300
- RTS/CPS and RTS Threshold are disabled on both 2.4 and 5GHz
- Regulatory Domain is set to United States on both 2.4 and 5GHz
Regulatory Domain is set to United States on both 2.4 and 5GHz
Any other ideas?
yeahuh, you might update to a recent DD-WRT build cause from your statement above there hasn't been no such thing in quite a while.... can't remember when but ---> only can set the reg domain in 1 place that takes care of dual band radios
Regulatory Domain is set to United States on both 2.4 and 5GHz
Any other ideas?
yeahuh, you might update to a recent DD-WRT build cause from your statement above there hasn't been no such thing in quite a while.... can't remember when but ---> only can set the reg domain in 1 place that takes care of dual band radios
Sorry, my bad. Most other options had to be set for both and I typed the RD part without checking. It is only on the 5GHz settings and I assume it applies to both.
I have been running the latest builds, it was 48741 for the last week or so, and today I updated to 48786. The last. time the issue happened (around an hour ago), it was on 48741.
Ok, I guess we need to know what clients are involved here - OS and wifi hardware (I don't recall seeing that information in the thread so far).
Macbook Pro 2018 (macOS Monterey 12.3.1) - Has never left the apartment since the issue started
Some old ASUS laptop (core2duo level of old, running Debian 11.3) - Has never left the apartment since the issue started
iPhone X (iOS 15.4.1) - Has never left the apartment since the issue started
Lenovo X280 (Windows 10) - Has not left the apartment in the last 2 weeks, but usually leaves once or twice a week
iPad Pro 2020 (iPadOS 15.4.1) - Leaves the apartment eventually (happened on Wednesday, but didn't seem to trigger the issue)
OnePlus 8 Pro (Android 10 I believe, can confirm later) - Leaves the apartment daily
Macbook Air 2015 (macOS El Captain 10.11.5) - Leaves the apartment daily
iPhone 11 Pro Max (iOS 15.4.1) - Leaves the apartment daily
And some other visitors' phones that I'm not sure about (usually Android).
Most of the time I notice the issue, it's shortly after the OnePlus 8 Pro left. But we also have noticed it when the iPhone 11 Pro Max does, with a ratio of 9 to 1 (9 times OnePlus, 1 iPhone). This may be just because the iPhone is mine and I'm usually the last one to leave, so I notice it when the other devices trigger it but my iPhone triggering is either if someone else is here and tells me, or if when I come back I see something failed, log into the router and see the messages I pasted before.
I'm not sure if my problem is the same as e-, but I received a lot of users complaints about unstable WiFi (Zoom meeting shows "unstable connection", WhatsApp unable to connect momentary) for the past few builds on my XR500.
I notice that when there are a few wireless clients connected (4-5 devices), everything are ok, but some strange issues occur when there are a lot of wireless clients connected (15-20 devices). After the issues happened, the issues persist even after most of the wireless devices have left the network. Only after rebooting router then the issues are gone.
Issues:
Devices are randomly disconnected from WiFi, even when very near to router and not in power saving mode (having Zoom meeting) : 1x Windows 10 PC with Intel ac WiFi card + 1x Windows 10 PC with Marvell ac WiFi card
Speedtest over WiFi is 10x slower than normal (normal: 300Mbps) although link speed is still showing 866Mbps. Speedtest over ethernet is not affected (300Mbps all the time). Issue is gone after rebooting router.
iPhone 13 frequently disconnects from WiFi "EEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)" <--- I disable "Disassoc Low Ack" and 802.11r (FT) and no more issue. After reading the posts above, the recommendation is to enable "Disassoc Low Ack". Can anyone with iPhone confirm that setting is safe? (I don't own any iOS device so I can't test myself)
I have MAC filtering, so all the guests are only allowed to connect to 2.4GHz network, while the 5GHz network is dedicated for PC with Zoom meetings.
It may be related to the fact that there are a lot of devices leaving/joining the network.
Attached are my current settings. I'm going to set "Protection Mode" to "None" and "Protection Mode" to "Disable".
Can I safely ignore the warning "ath10k_pci 0001:01:00.0: failed to lookup txq for peer_id xxx tid xx"?
Can I safely ignore the warning "ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode"?
My boss is getting impatient that I can't get the WiFi working properly for the past few weeks. Is there any build/setting that is stable for AP mode?
We could troubleshoot settings but everyone has their own ideas what is best.
I have TurboQAM Disable, WNM Mixed, BI 100 DTIM 2, Protection Mode None,
RTS Threshold Disabled, ACK Timing 500 (900) 1350, Short Preamble Enable.
Roll mostly safe defaults certainly no TurboQAM or RTS/CTS wrenches thrown.
I keep Wireless Security settings all defaults except of course SSIDs and keys.
So for WPA2 Personal and CCMP-128 (AES) these are the only boxes checked.
Edit: also U-APSD Disable and Disassoc Low Ack Enable, all defaults you get it.
Last edited by blkt on Fri May 06, 2022 10:32; edited 2 times in total
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Fri May 06, 2022 10:27 Post subject:
country domain is Canada(for best use Canada or Haiti)
Short GI - enabled
Diassos low ack - disabled...its safe to disable it...
Sensitivity Range ACK timing - mine is to 900
its odd couse i have lots of disconnects and reconnects in (R7800) syslog, but they seem to be very quick and not impacting clients performance...or at least no complains so far...
the crazy issues i ve over wifi, form year ago, is 1 of my W10pro needs to be 3-4 times reconnected, as it disconnects/drops wi-fi connection and than its ok after 3-4 try's and connection is stable...and can last a days...
I tried to change to another external WiFi dongle and its the same...so, i have to admit its something with W10pro crap drivers to blame, as BS pointed it out back in the days...but, i can live with it...oddly enough it happens only on one W10pro all the rest W10Home editions not affected ...nor any Linux or iPhone/Android devices using the R7800 2.4Ghz WiFi.. _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Last edited by Alozaros on Fri May 06, 2022 10:34; edited 2 times in total
The disconnection issue was with 5GHz devices (I didn't care about 2.4GHz guest), but I'll disable TurboQAM just in case.
I'll set Wireless Network Mode, U-APSD disabled, BI, DTIM, Protection Mode, RTS Threshold, Short Preamble Enable, ACK Timing 500
I'm lost and I don't want to deviate too much from tested working settings.
Yes, I did have that nvram erase step when coming from stock (followed ecg guide). After that all settings are manually entered.