NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - RBR850 / RBS850 Firmware Version v4.6.7.5 Released
No Release Notes at this time. I'll see if I can get some.
Download Link:
https://ntgr.my.salesforce.com/sfc/p/#300000000xsV/a/8b000000saFy/gnaaQgriSv_NWgvrN.dvn786cl4eG45R2.62LEI3edU
F...
Over the last few days, Chuck_M and I have been working together to try and resolve the Hop Count issue I've been observing on one of my satellites - I thought I'd post our findings here in case it is of use.
Observed behaviour: in the debug page for my wired RBS satellite, the Hop Count shows as 1 (as you would expect) immediately following a reboot, but between 24 and 36 hours later, this switches to a value of 255. It then stays at 255 until the system is next rebooted. While this doesn't impact performance of the satellite or network as far as I can tell, we were concerned that it represented some sort of underlying issue that we might be able to resolve. I also have another satellite that is connected wirelessly and this consistently stays at 1. The router is in AP mode.
Things we've tried to resolve this:
- switched the satellites over, to see if this was some kind of hardware issue. The issue remained with the new satellite in the same position, so it does not appear to be specific to a single device.
- observed behaviour to see if this was connected to specific devices or activity - unable to identify any underlying causes or manually recreate the issue. At one point the switch occurred overnight when network activity was minimal. It appears to be time-related more than anything, i.e. the value will always remain at 1 for the first 24 hours following a reboot then change at some point in the next 24 hours.
- reconfigured the network; previously the satellite sat behind a switch, we swapped these around so the satellite was the first device in the chain. Not only did this not resolve the problem, it introduced instability, and the satellite started rebooting itself periodically. We reverted the change so the satellite is behind the switch again and it is no longer rebooting itself.
- tried removing all other devices from the switch to see if this changed the value back from 255 to 1; it did not.
- tested all cables and all are fine.
I haven't tried a full factory reset and to be honest I'm not willing to do this unless the issue starts causing network instability or other problems, which at the moment it is not.
So we haven't resolved the issue. I am now wondering if this is some sort of firmware problem, I would be very interested to know what values for Hop Count other people with wired satellites are seeing on the debug page - especially those whose systems have been running for some time.
Huge thanks to @Chuck_M for his patience and assistance with all of this, he is a helpful and knowledgeable guy.
Garwoofoo wrote:Over the last few days, Chuck_M and I have been working together to try and resolve the Hop Count issue I've been observing on one of my satellites - I thought I'd post our findings here in case it is of use.
Observed behaviour: in the debug page for my wired RBS satellite, the Hop Count shows as 1 (as you would expect) immediately following a reboot, but between 24 and 36 hours later, this switches to a value of 255.
Maybe it's just reporting a wireless backhaul hop count setting.
255 -> wired backaul has higher priority
kolella wrote:
Garwoofoo wrote:Over the last few days, Chuck_M and I have been working together to try and resolve the Hop Count issue I've been observing on one of my satellites - I thought I'd post our findings here in case it is of use.
Observed behaviour: in the debug page for my wired RBS satellite, the Hop Count shows as 1 (as you would expect) immediately following a reboot, but between 24 and 36 hours later, this switches to a value of 255.
Maybe it's just reporting a wireless backhaul hop count setting.
255 -> wired backaul has higher priority
wireless.BhAp2.wps_pbc='3'
wireless.BhAp2.wps_config='virtual_push_button physical_push_button'
wireless.BhAp2.root_distance='255'
wireless.BhAp2.rts='64'
wireless.BhAp5=wifi-iface
wireless.BhAp5.network='backhaul'Aaaand I've just spotted the same wired satellite "rebooting" (loss of connectivity followed by flashing white lights and then a solid blue light) completely at random in the middle of the day. So I guess that problem isn't resolved either, I don't know if it's connected to the Hop Count 255 issue or not. I'd thought that setting CTS/RTS to 500 had resolved this random reboot issue and while it may have helped, it clearly hasn't completely prevented this behaviour.
Worth noting that it's not a complete reboot: the system uptime for the satellite has not reset.
This appears to be the same problem described in this thread:
In that case the poster went through two different Orbi sets and multiple firmware updates/factory resets without ever resolving the issue, eventually giving up and replacing the set for a competitor's brand.
Exasperated now, I've checked all the physical connections and cables (as did the poster above) and like them, I'm now convinced this is a firmware issue. It certainly seems specific to wired satellites. I hope Netgear roll out something new soon.
(never mind - post deleted)