I have three Netgear Routers: WNDR3700, WNDR4000, and WNDR4500.
On the SAME wired network, the 3700 works great. But both the 4000 and 4500 exhibit the same symptom. They periodically drop WAN connections for a minute (almost exactly), then allow them for 5-20 seconds, drop them for another minute, etc. In the plots below, red in the time graphs means that traceroutes and pings are not getting returned by the affected hops along the path (top part of the plots).
Existing connections (Netflix streaming) seem to not be affected. I see this periodic dropping clearly doing traceroutes or pings. Pingplotter is especially effective at showing this.
This is what a normal Pingplotter connection (on the WNDR3700) looks like:
It is normal for the destination (the Comcast nameserver) to refuse to answer some packets. The white area on each plot is the jitter, which increases up to a loss, and then drops.
What could be causing this?
Snoopytime on the Netgear Forum suggested:
Try going to Setup, then to WAN Setup . . then UNCHECK 'IGMP Proxy Disable'.
I think I figured it out. Pingplotter sends multiple ICMP requests. The router apparently has trouble dealing with these when queued up.
I modified Pingplotter to send them serially, and the problem went away.
So what is causing it? Well, someone on the forum said that what happens is that the router loses its DNS addresses. This would be consistent with my symptoms during the periodic outages: existing connections continue to work, new ones do not. The person suggested that I put in the fixed Comcast DNS addresses (22.214.171.124 and 126.96.36.199). But I also installed the latest Netgear beta firmware which he said supposedly fixed things. And it has been working using the unmodified Pingplotter for 14 hours now.
Hi, Jim !Your Easy guide is really very good. I tried to search for the answer on the Internet. I tried many websites but did not get proper answer. on other web sites, you will get only the information about the router but not the step by step resolution. I called the manufacturer of my router but they did not help me as my router was not in the warranty period. First I was thinking not to go for your Easy guide. I tried a lot on the web site but could not make it. Finally I tried your Guide and got it connected. There are many problems described in your program. Thanks for such a wonderful program. You saved my money.
Hi - in truth great site you have created. I enjoyed reading this posting. I did want to publish a remark to tell you that the design of this content is very aesthetically delightful. I used to be a graphic designer, now I am a copy editor. I have always enjoyed functioning with information processing systems and am trying to learn code in my free time.
Drupal makes it easy to design a pretty Web site.
Routers must be patched just like any other computer equipment!
"Low-priority databases containing temporary network workload information could be a perfect vector for simple SQL injection attacks, which can lead to outright domination of WiFi routers given the right chain of attack. So warns a Black Hat presenter who, in a few weeks, will show how he used SQL injection attacks to put together attacks that lead to remote takeovers of SOHO routers."
Linksys routers are vulnerable too:
Be sure that you buy a new cable/dsl modem occasionally. For cable, you want one that supports Docis 3. This allows you to use channel bonding for higher speeds. I updated my old surfboard modem to a new Docis 3 model, and my speeds increased 50%