Does your Netgear R7000 lock up on you, and what is your downlink speed?
No, <100 Mbit/sec
16%
[ 1 ]
No, 100-300 Mbit/sec
16%
[ 1 ]
No, 300-500 Mbit/sec
16%
[ 1 ]
No, 500+ Mbit/sec
50%
[ 3 ]
Yes, <100 Mbit/sec
0%
[ 0 ]
Yes, 100-300 Mbit/sec
0%
[ 0 ]
Yes, 300-500 Mbit/sec
0%
[ 0 ]
Yes, 500+ Mbit/sec
0%
[ 0 ]
Total Votes : 6
Author
Message
rlk DD-WRT Novice
Joined: 02 Jan 2020 Posts: 2
Posted: Fri Jan 03, 2020 0:33 Post subject: Netgear R7000 lockup with multiple builds
I recently purchased an R7000 to replace my R6300v2, for performance reasons. The problem is that after a while (where "a while" ranges from about 30 minutes to 3 hours-ish) the router locks up as described below.
There have been a lot of posts with similar symptoms; many people are not able to reproduce it, though.
First, network topology: I have 500/25 service, via RCN business class cable. The RCN router is connected to my DMZ net (192.168.0.0/24); my internal router bridges the DMZ to my internal network (192.168.1.0/24) in addition to providing domestic wireless service (I prefer to use my own than the ISP provided service). I have a server that's dual homed but doesn't forward packets.
Running speedtest from my server, I get an initial burst of about 900 Mbits down that decays to 700-750 (and presumably after long enough would decay back to 500). With the R6300v2, I'm limited to about 350-400 Mbit/sec, wired or wireless, including, transfers from an internal host to the DMZ address of the server. I'm aware of the 450Mbit/sec limit using NAT, but I'm not using NAT on my internal router. The R7000 is quite capable of achieving the full line speed wired, and wireless internally I can get about 75 MBytes/sec (600-700 Mbit/sec) single stream for a multi-GByte transfer, which isn't bad in a fairly dense suburban neighborhood.
The problem is that the R7000 will run for a while, and then lock up: it won't respond to ICMP echo and wireless goes off the air, although the lights continue to behave as normal. This has happened with the following builds (note that in all cases, I did 'erase nvram' followed by flashing the firmware via web UI)
- 40559 (Brainslayer, was most current at time of download)
- 36410 (Brainslayer)
- 40270 (Kong)
- 36440 (Kong)
- 28600 (Kong)
The last is the build that I have been running on the R6300v2 with no problems (obviously, using the R7000 .chk). It does not achieve the same performance as the others, peaking at about 600 Mbit/sec wired and 400 Mbit/sec wireless. I'm using the same configuration in every way that I have determined (except for the DMZ static IP address, different only in the last octet but there's no collision) on the R7000. There may be a correlation between doing heavy data transfer and the R7000 going catatonic. There are no log messages that I could spot prior to this happening (via the web UI).
I'm not absolutely positive, but I believe I did get one clean prolonged run with only one wireless client (using a different SSID) looping on a speedtest, for about 440 cycles (probably 6-8 hours).
The configuration I use is as attached (passwords and such sanitized); only non-default settings relative to build 40559 are listed. To repeat, this is the same configuration I have used for a few years on the R6300v2.
I've tried the following changes; none have any effect on either performance or functionality:
I've also tried different 2.4 and 5 GHz channels with no effect on the outcome, but with performance differences (at 5 GHz, selecting any channel yields better performance than Auto, but there's one channel that yields worse performance than the others presumably due to local airspace).
Joined: 18 Mar 2014 Posts: 12887 Location: Netherlands
Posted: Fri Jan 03, 2020 10:56 Post subject:
40559 is not the best build, do not use the router database see below
I took a peek at your configuration, as this seems your down stream router I have my doubts about setting a static route and also with the port forwarding you are doing
Static routes are necessary to set on your upstream router pointing to your down stream router if your down stream router is in router mode or you want access from upstream to downstream.
Attached my notes how I link two routers while both being on different subnets.
Furthermore I would set my secondary router on automatic DHCP and set a static lease for that router on my primary router but that is just me
The correct command to reset to defaults on recent builds is: nvram erase && reboot
older builds have: erase nvram
Usually the R7000 is rock solid
Below some pointers which might help to get the best out of DDWRT and out of the forum:
1. Research your router, start with the supported devices wiki:
https://wiki.dd-wrt.com/wiki/index.php/Supported_Devices .
2. In the supported devices wiki you can see if your router is supported and what architecture your router has and if you are lucky also an install guide/wiki.
3. Post in the right forum, from the former step you can see if your router is Broadcom, Qualcomm/Atheros, Marvell or other, use that forum to post router specific questions, for networking questions post in the Advanced Networking forum and for other things in the General Questions forum.
4. When posting always state router model, build number and when applicable the Kernel version.
Describe your problem and how you think it can be solved.
Give as much detail as you can also provide your network setup if applicable.
For your Network setup, state what wiki you have used: https://wiki.dd-wrt.com/wiki/index.php/Linking_Routers
5. When posting pictures make sure the maximum width is not more than 600 pixels.
6. Do not hijack a thread, meaning do not post your own problem in someone else's thread. Just start your own thread. This so that it can be searched and found by others.
7. If your post is answered and your problem solved, mark your thread with [SOLVED] (the header of your first post).
8. Do NOT use the router database, builds can be found at:
https://dd-wrt.com/support/other-downloads/?path=betas%2F2019%2F
All builds are beta including those from the router database.
9. Before uploading a new build to your router, research the build by looking in the build threads.
This is an example of a build thread for build 41686 for Broadcom routers:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=322339
Search build threads with the search function and search on build number.
10. Use the build threads from the former step to report success or problems.
11. For older Broadcom routers (Linksys WRT54 and E series) read the peacock thread although some of it is outdated: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=51486
Builds can be found in the Broadcom directory for Linux kernel 2.4, in Broadcom_K26 for Linux K2.6 and in Broadcom_K3X for Linux K3.X.
12. If you are sure you have discovered a bug, after asking and querying the forum, you can report a real bug in the bug tracker: https://svn.dd-wrt.com/
This is also the place where the commits/changes to the source are administrated.
13. Recommended reading:
https://forum.dd-wrt.com/wiki/index.php/Main_Page https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=54845 https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=54959
14. If you are happy with DDWRT and want it to live on then donate:
https://dd-wrt.com/donations/
40559 is not the best build, do not use the router database see below
I took a peek at your configuration, as this seems your down stream router I have my doubts about setting a static route and also with the port forwarding you are doing
Static routes are necessary to set on your upstream router pointing to your down stream router if your down stream router is in router mode or you want access from upstream to downstream.
Attached my notes how I link two routers while both being on different subnets.
Furthermore I would set my secondary router on automatic DHCP and set a static lease for that router on my primary router but that is just me
The static route is set up on my upstream router. However, I want to be able to access the external IP internally. Dynamic DNS would probably be a better way to go...but...
I've been running DDWRT for over 10 years, starting with the original linksys hardware WRT54 and it has generally been stable.
My main router is an R7000. I was running a Jan-2021 beta version and it worked fine till 2 days ago. Then it started locking up, sometimes within 10 minutes, yet other times, every few hours. At first, I thought hardware failure, so I saved the configuration and replace it with another R7000 I had. Same thing--it still locks up. I updated the firmware to the latest 2021-03-26 beta. Still locks up. Switch no longer works and I get no responses from pings.
I starting wondering what setting did I changed that might have caused this. I started flipping switches in DDWRT to test. It turns out the problem occurs when I enable UPnP. I have network device that otherwise uses UPnP. Turning UPnP off on the router has solved the lockups for me.