Posted: Mon Jun 10, 2019 5:57 Post subject: Beacon numbers for radiation/congestion reduction settings.
Prime beacon interval numbers don't readily collide with other wifi access points. Update: However, that may be incompatible with recent IOT updates, such as Google Home and some Marvell clients (some of those need beacon divisible by 100).
For rf sensitive people, longer time in-between 2.4ghz beacons, such as 300, prevents headache.
You can leave the 5ghz on the default setting.
Other tip, Try DTIM set to 2 to enhance phone and tablet power saving.
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Fri Jun 28, 2019 20:54 Post subject:
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.
Joined: 08 May 2018 Posts: 15539 Location: Texas, USA
Posted: Mon Jul 01, 2019 9:55 Post subject:
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.
...I'm in an apartment complex with lots of signals flying around.
...
Just wondering about the client bridge interval issue.
For an apartment with wifi congestion, CTS to auto and lowering the RTS value could help. Lower RTS costs some throughput but reduces lag, and can get more range for 5ghz. Theoretically, the setting could be done at clients or access points; but, it is usually done at the access point.
Client-mode specific WL commands exist but they aren't represented in the user interface; and, clients don't beacon. So, generally, those settings are done at the access point.
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
Joined: 21 Jan 2017 Posts: 1797 Location: Illinois Moderator
Posted: Mon Oct 26, 2020 15:19 Post subject:
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. _________________ FORUM RULES
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.
Thanks for the good info. Made the changes to all 3 sites in my Signature. I will report back... _________________ Home Network on PureFibre 500Mbit/s - 10GbE Copper Backbone
2x R7800 - Gateway & AP & 3xWireGuard - DDWRT r53562 Std k4.9
Off Site 1
R7000 - Gateway & AP & WireGuard - DDWRT r58389 Std
R7000 - Station Bridge - DDWRT r49626 Std
Off Site 2 - Wired Backbone
3x R7000 - Gateway+AP01 / AP02 / AP03 - DDWRT r58389 std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
Joined: 21 Jan 2017 Posts: 1797 Location: Illinois Moderator
Posted: Tue Oct 27, 2020 0:09 Post subject:
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... _________________ FORUM RULES
well then again, I am in a more-or-less non-congestested place ...very small town setup.
but then again again, in other town I recently fixed problem folks were having connecting mutiple devices -- ( I put their ZITO cable WiWimodem in bridge mode) setup an oldass E2500 to suit their needs and also PW they liked and all has been good for month now.
yeahuh--- it is real 2.4 congested area but they are happy now -- so I'm happy