NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
R7960P - Router failing or?
Unusual Problem just cropped up. The router fails to work periodically. When that happens lights all seem to work (lit or flashing periodically) except you can't connect to the router. Interesting...
The modem is hard to get to, it is a ISP Charter supplied modem (Spectrum make Docsis 3.1 rating).
Cable is either Cat 6 or Cat6/E. Top of the line patch from mono price.
Yes I performed such a cycle before the last 12 hours between failure. But the majority of time I just have been shutting of the router, waiting 30 sec and turning it back on.
No I have not done a factory reset from scratch. I will consider trying such a move, but keep in mind the last firm ware upgrade was several months ago, and this problem only showed up a couple weeks ago.
I am trying one change at a time, want to see how this IPV6 change (from 6to4 to DHCP) impacts things. If still happening, I will first try turning IPV6 off. Then I'll try a reset.
My DHCP pool is already restricted .002 to .037.
Does turning on IPV6 stress the router more (especially the 6to4 tunnel setting)?
No the router is warm but not at all hot. I also blew it out with compressed air to make sure no dust impeding cooling transfer.
So far, after the change to DHCP on the IPV6, it has not crashed yet and I have hit the 12 hour mark (fingers crossed)
Auto should be used for IPv6. I think 6to4 is being depreciated.
Let us know how it turns out.
Yes, I am not sure how 6to4 tunneling was originally set, I thought when I turned on IPV6, I specified Auto Detect. But 6to4 is next option in list so maybe I overshot.
So far its been stable for 24 hrs but I am monitoring. Do you know how routing works with IPV6 and IPV4 turned on simultaneously? IS there an attempt to route via IPV6 first with the IPV4 attempt a fallback?
I believe routing tries with IPv4 first, then IPv6, even if your ISP doesn't support native IPv6 services, seems like the router checks the IPv6 path when enabled.
There is a known problem in the IPv4 DNS stack across all R series routers that causes a delay in DNS handling. Thus users see a DNS error message in browsers here and there. Some browsers can continue past this while others don't. Some one just happen to stumble across enabled IPv6 (Auto) and seems to be a work around. We've let NG know about this.
Yes, I am familiar with the DNS stack timing problem which showed up with the newest firmware release. I saw it on any chrome based browser (Chrome, Edge).
Interestingly enough, I notice that choosing the auto config option seems to result in another one of the options on the list being ultimately selected after a routine executes (most recently in my case, DHCP). Out of curiosity, when others have run the autoconfig option, what has been the result for them, DHCP? or a range of options dependent on ISP?