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...
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)