[danielwritesback]

See attached chart for valid beacon interval numbers. The prime numbers aren't masked by or collide with other wifi access points.

For rf sensitive people, longer time in-between 2.4ghz beacons, such as 293, prevents headache.

Other tip, Try DTIM set to 2 to enable phone and tablet power saving. Preventing wake-locks saves battery and reduces wifi congestion.

See also https://play.google.com/store/apps/details?id=com.pzolee.wifiinfo Wifi Network Analyzer phone app--you probably don't want the 2.4ghz signal more than halfway up the scale if measured from your bedroom.

[SinCalChewy]

This post has been super helpful, as I'm in an apartment complex with lots of signals flying around.

My only question: I have client bridges on my network to the gateway. I have the beacon interval set there, and currently on my client bridges as the same. Should client bridges have the same interval? Or is it better off having a different interval than the gateway?

DTIM at 2 has helped a lot as well. Just wondering about the client bridge interval issue.

TIA!

[kernel-panic69]

Setting 2.4GHz band to 293 and 5GHz band to 241 seems to be working good on my E4200 v1. I left the GTK renewal at the default of 3600 and so far, NO ISSUES, save and except for the first couple of hours of uptime after I had to de-brick after a bad flash on 40167. Currently still using 40065 K3.x mega.

[tinkeruntilitworks]

i would get some errors that would accumulate over time. always still "100%" though. never noticable.

i adjusted the beacons to primes and the dtim to 2. i haven't seen any errors since it's been up and running.

for some reason when my phone first connects it sends packets that are errors. then it quickly resolves the issue.

those initial errors are all I've seen. thanks for posting

[bushant]

More about which prime numbers to use:
https://www.dslreports.com/forum/r14241618-Theory-on-Optimizing-a-802-11-Beacon

[dTX]

DEV's,make this post Sticky please. It's very informative and beneficial to everyone here.I also had no idea about the proper interval numbers.
danielwritesback thanks for posting this !!!!

[danielwritesback]

[danielwritesback]

Another source of congestion is junk packets. CVE-2019-11477 CVE-2019-11478 CVE-2019-11479
To fix, you can use:
iptables -t mangle -A PREROUTING -p tcp -m conntrack --ctstate NEW -m tcpmss ! --mss 536:65535 -j DROP

[msoengineer]

For the moment, the following is what is recommended:

Use 300 for the beacon interval for the primary radio you want seen first (5ghz most likely). DTIM should be 1.

Use 400 for the other radio if you have a router with two radios. DTIM should also be 1.

Enable RTS/CTS and then set the separate box for threshold to 784.

mtu=1500 bytes divide by half to yield 750 plus 34 bytes for overhead = 784.

prime numbers for BI may prove problematic for some client devices and YMMV if you use a prime number. 300-600 is the "sweet spot" for beacon interval vs. client power consumption. 300 seems to be a BI time unit recommended by advanced network guru's.

[itwontbewe]

R7000P here
the RTS/CTS looks different than your qca settings

do i just set rts threshold to 784 and leave the rest as is? is the fragmentation threshold related to it as well?

[msoengineer]

Set both thresholds to 784.

[itwontbewe]

thank you

[mac913]

[mrjcd]

just a note --
all my brcm WAPs & Gateways I have:
Fragmentation Threshold 1792
RTS Threshold 1792

AND also

all QCA units - gateways & WAPs:
Protection Mode RTS/CTS
RTS Threshold Enabled
Threshold 1792

has worked very well for me for couple years

[msoengineer]

I think anything set higher than 1500 will make no difference for wifi to wan traffic. For wifi to lan that 1792 might still be useful, but wan traffic is 1500 bytes or less making 1792 similar to 2346...