Posted: Thu Feb 28, 2019 1:39 Post subject: Consistently having problems with 5GHz radio on newer builds
For quite a while I stayed on R37945 with my R7500v2 because it was so stable. I think I then jumped to 38150 and have also tried 38500 and 38535.
Without having made any changes to the wi-fi settings, each one of these newer builds has introduced a problem whereby the 5GHz radio only allows download speeds from the WAN to clients to hit ~5Mbits, as opposed to my usual ~150Mbits.
If I make any change to the 5GHz radio settings--say, for example, changing the channel or turning on/off beamforming, etc.--it'll return to normal, but only temporarily. It'll probably flare back up a few hours later.
Sometimes it takes days for the problem to arise, but when it does, it usually continues to flare up until the router is rebooted.
For a while on dd-wrt Kong builds, I've been using AC-N Mixed, 161 LL, noise immunity ON, short preamble ON, short GI ON, protection mode NONE, both single and multi-user beamforming ON, and airtime fairness ON.
I've tried turning off some of these things, but the problem comes back pretty quickly afterwards usually. I've not spent the time to apply these changes and then reboot after each one to try to isolate, only letting the radio re-initialize.
Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Thu Feb 28, 2019 4:05 Post subject: Re: Consistently having problems with 5GHz radio on newer bu
bripab007 wrote:
For quite a while I stayed on R37945 with my R7500v2 because it was so stable. I think I then jumped to 38150 and have also tried 38500 and 38535.
Without having made any changes to the wi-fi settings, each one of these newer builds has introduced a problem whereby the 5GHz radio only allows download speeds from the WAN to clients to hit ~5Mbits, as opposed to my usual ~150Mbits.
If I make any change to the 5GHz radio settings--say, for example, changing the channel or turning on/off beamforming, etc.--it'll return to normal, but only temporarily. It'll probably flare back up a few hours later.
Sometimes it takes days for the problem to arise, but when it does, it usually continues to flare up until the router is rebooted.
For a while on dd-wrt Kong builds, I've been using AC-N Mixed, 161 LL, noise immunity ON, short preamble ON, short GI ON, protection mode NONE, both single and multi-user beamforming ON, and airtime fairness ON.
I've tried turning off some of these things, but the problem comes back pretty quickly afterwards usually. I've not spent the time to apply these changes and then reboot after each one to try to isolate, only letting the radio re-initialize.
Does anyone have any ideas?
Thank you.
Before performing a factory reset- which may fix things...
See my signature for best qca settings for beacon interval.
Turn off MU-MIMO and turn off noise immunity. _________________ FORUM RULES
LONG/SHORT:
Choosing from among a list of prime numbers makes it less likely that your beacons will "chirp" in sync with the beacons of other networks. Since beacons can collide as well, it makes sense to choose an interval that is unlikely to align with neighboring networks for very long. _________________ FORUM RULES
LONG/SHORT:
Choosing from among a list of prime numbers makes it less likely that your beacons will "chirp" in sync with the beacons of other networks. Since beacons can collide as well, it makes sense to choose an interval that is unlikely to align with neighboring networks for very long.
Slightly off topic, but using prime numbers is the same trick cicadas use not to all come out in the same year. See this link
I just upgraded to the R38840M Kong build, so I guess I'll wait to see how that one goes before I make any other changes.
Yes, I had left the beamforming on both my R7500v2 main router and my broadcom R7000 WAP for a long time because it always seemed to work fine. I haven't really played with any of my settings for a long time because they'd been so solid.
My traditional settings on the R7500v2 have been:
AC/N-Mixed
VHT80
161 - LL
default tx power & antenna gain
U-APSD - Disable
Noise immunity - Enable
Protection Mode - None
RTS threshold - Disable
Short preamble - Enable
Short GI - Enable
Single user beamforming - Enable
Multi user beamforming - Enable
default tx/rx chains
AP isolation - Disable
Beacon interval - 100 (I'll change this to a prime #)
DTIM interval - 2 (default)
Airtime fairness - Enable
Frame compression - Disabled
WMM support - Enable
Radar detection - Disable
scan list - default
Sensitivity ACK timing - 1350
Max associated clients - 256 (default)
Default for all "Drop clients with low signal" config _________________ Netgear R7500v2, DD-WRT v3.0-r37845M kongat
Netgear R7000, DD-WRT v3.0-r37715M kongac
Thanks again for taking the time to post your settings. I finally found a setting that appears to have made a discernible effect: airtime fairness set to disabled.
After setting ATF to disabled, I've been running speed tests on various devices in various parts of the house, and it has yet to revert to the weird slow 5GHz radio behavior.
So I posit that either a) doing a bunch of ddup upgrades without ever clearing NVRAM and re-config'ing has finally caught up with me or b) there's been some change in the Qualcomm drivers with regard to ATF that is affecting my devices and/or a bit buggy with the R7500v2's IPQ806X chip. _________________ Netgear R7500v2, DD-WRT v3.0-r37845M kongat
Netgear R7000, DD-WRT v3.0-r37715M kongac
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Mar 03, 2019 19:55 Post subject:
drivers for qca9984 are complete shit right now, and ddwrt's "behind the scenes" auto tuning/lack of "advanced" features isnt helping _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
