NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - RBRE960 / RBSE960 Firmware Version 7.2.6.31 Released
Enhancements: 03/22/2024
(For all regions except Europe)
Improves the stability of WiFi device connections during roaming
This firmware addresses security vulnerabilities. For more informatio...
I have noticed issues that only seem to crop up after days of running - as few as 3-4 days, as many as 22 days. They are router or satellite restarts, memory growth in satellites to the point of causing a reboot and disconnect of all devices. I have seen WiFi disconnect and stop working until the router was rebooted. Have seen IPv6 stop working until it was re-enabled (likely a Comcast-NG interaction issue). I have seen satellites lose their backhaul connection with the router.
I believe at least the memory creep issues are related to using 2 satellites on Ethernet backhaul, just a guess. It could also be related to higher speed networks, mine is a 2G/200MB service. Maybe it's a combination of different factors that make the perfect storm that problems can appear? The % of Netgear customers with 2G and multiple Ethernet-wired backhaul satellites is small, I suspect. Plus, if there are some bugs that pop up after a number of days of running, NG has said that this kind of testing is very hard for them to do.
I just went back to v.21 to see how it runs. If v.31 is working well, great - if not, some caution could be warranted to try V.21 before spending lots of time trying to find a problem.
Updated my two satellites and then the router. No problems. Found that it changed my IPv6 DNS settings to get from the ISP rather than the ones I manually entered previously. Changed those back to the manual settings (to what the ISP uses!) , and discovered IPv6 DNS doesn’t work with Armor Web Protection turned on. Turned it off and no problems.
Thanks for the update owlyn !! So you are back to using Manual IPv6 settings again? If I could ask, if you go to 192.168.1.1/debug.htm (or whatever your router IP address is), how much memory is it using, probably out of 818MB available? And who is your ISP?
owlyn wrote:
Updated my two satellites and then the router. No problems. Found that it changed my IPv6 DNS settings to get from the ISP rather than the ones I manually entered previously. Changed those back to the manual settings (to what the ISP uses!) , and discovered IPv6 DNS doesn’t work with Armor Web Protection turned on. Turned it off and no problems.Ah - I wonder if this why my manually set DNS caused problems. I have Armor on as well. When I have some time, I will try it again with Armor off. For curiosity only though - IPV6 with the DHCP'd Comcast DNS still fine here.
Unfortunately I randomly started having satellites disconnecting, so I had to downgrade back to "Firmware Version 6.3.7.10", since I am in the EU region.
Since I don’t have time to keep troubleshooting the issue, I am going to stay on the older firmware until Netgear iron out the bugs.Thank you for letting us know.
