Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Tue Jan 28, 2020 15:39 Post subject:
You didn't follow my suggestions that are in my signature below. So I am calling you to the mat....
Several things wrong in 2.4ghz:
-Change TX power to 30- I believe your chipset will top out at 24, but I don't recall off the top of my head, maybe 27. (Same for 5ghz, make it 30)
-Turn off Noise Immunity- it can affect throughput
-Set Protection mode to RTS/CTS
-Set the RTS threshold to 980
-Turn on Short Preamble
-Set the beacon to 181
-Change ack timing to 3150
FOR 5ghz.
You really should name this the same as your 2.4GHZ to alleviate some of the overhead. (SET BEACON TO 101 to make sure 5ghz connects first on your clients- swap the two intervals if you want 2.4ghz to be first seen by clients)(Also, make sure the password is the same for both 2.4&5 if you decide to make it all the same name)
-Set wifi mode Mixed (Don't use dynamic)
-Select Lower if using 161.
-turn off noise immunity
-Same RTS/CTS as 2.4ghz
-turn on short preamble
-set ack timing to 3150
See how that starts working... _________________ FORUM RULES
I can assure you that the settings I suggested are not the cause of the issue. Something else is at fault.
I agree completely. I have using DD-WRT on it for over 5 years, with me updating it once every other month until the issues started.
msoengineer wrote:
Are you doing anything else with the router aside from simple AP usage?
The only things I have it doing are the following :
Internet routeing
Internal network routing
open DNS IP updateing
Wireless AP
DHCP server
Reserved IP addresses
Port forwarding
I believe that is all.
msoengineer wrote:
Also, please confirm you have a v1 of the router and not v2 or v3... only the v1 is supported by dd-wrt.
Oh yes, I have the v1 version of the router. I have no version number next to the model listing, and I got this a few months after it was originally released.
Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Tue Jan 28, 2020 23:32 Post subject:
Then use the settings I gave you on the last build that works and things should be better.
I've seen no one else complain about their WNDR4300....maybe you have a power supply going bad or capacitors going bad too...Flakey power supplies can do strange things. _________________ FORUM RULES
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Wed Jan 29, 2020 3:57 Post subject:
1031982 wrote:
It just seems odd to me that any build before it works.
Any idea where to get a replacement power adapter?
Search Google, eBay, and Amazon for "Netgear WNDR4300 power adapter". At a bare minimum, you want 12V 1.5A DC output, but 2A will work fine (might actually work better if it's 2A or 2.5A). The thing is, if your power input filter caps are shot, it may not do anything to fix or improve the situation to get a new power adapter. You may want to carefully inspect the capacitors or go ahead and replace them as well. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Ok, the capacitors are all fine. After pulling them, and checking with my multi-meter, they are all in range.
My power supply is already 2.5A. The exact model is P030WF120B.
If I get a new power supply and still have issues, should I even bother posting again? It seems that if replacing the power supply doesn't fix this, there are no other ideas.
