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.
reddavin FURRYe38 It could be related - losing connectivity could be Hop Count gone to blank. When that happens, devices won't connect to that Satellite, and they could easily be too far away from anything else to connect - hence the disconnected state.If you notice sometimes it's connected sometimes it's not, it could be 1 satellite and the router are fine - so moving within range of them establishes a connection again. Maybe it's reconnecting via 5 GHz or 2.4GH from somewhere else too.
This could also be a symptom of the router restart. Bringing up a system (power cycle, reboot) with 2 Eth-connected back hauls also is problematic.
My procedure now, if I have a reason to power cycle or reboot the router, is power cycle the RBSs once the router is up. Go to 192.168.1.1/debug.htm and monitor Hop Count, make sure it says 1. If it does not say 1 after say 20 minutes, power down that RBS, take it next to the router, power it up, let it sync wirelessly (wait for the Blue LED). The power it down, place it in its normal position, connect the Ethernet cable, and power it up. It should sync fine and Hop Count should stay 1.
My router has now been up just about 2 days, with all fine here. I am also running IPv6, the only difference is I have manually set the IPv6 DNS servers to Google's:
2001:4860:4860::8888
2001:4860:4860::8844
donawalt wrote:
My procedure now, if I have a reason to power cycle or reboot the router, is power cycle the RBSs once the router is up. Go to 192.168.1.1/debug.htm and monitor Hop Count, make sure it says 1. If it does not say 1 after say 20 minutes, power down that RBS,.....
(Sorry, I have no 960 to look at and none of the devices I have display a "hop count") Can you please clarify:
- 192.168.1.1 is the router, correct?
- Does the router display "hop count" for each of the attached satellites?
- Or, is the debug page of each satellite being monitored to observe "hop count"?
(I am easily confused and would rather admit it than remain confused.)
No - You will have to get to the debug pages of the satellites by first getting their IP address from your "Attached Devices" link under Basic, when you log in to the Routers Web page (like for me, 192.168.1.1). Find the IP address of the RBSs - check them both - type 192.168.1.yyy/debug.htm (where 192.168.1.yyy is the address of each RBS from the Attached Devices list), log in with your admin log in to the router, and you'll see a page like the one I showed above - you can see Hop Count.
Does that help?