NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - RBR850 / RBS850 Firmware Version 7.2.6.21 Released
New Features: 09/08/2023
Supports Separate SSID IoT network.
https://kb.netgear.com/000064267/How-do-I-enable-or-disable-the-Internet-of-things-IoT-network-on-my-Orbi-WiFi-6E-System https://...
Update went smooth, no issues so far.
I've been using this firmware for several weeks and largely believe experience has been good. I do believe there's a bug, however, in the web interface. It regularly reports one of my satellites with a "poor" backhaul status:
Things always showed "good" under previous firmwares and I didn't move the locations of my Orbi devices. When I view the system via my phone app, it reports all "good". Additionally, when I power-cycle my system, I receive the blue light on satellite #2 indicating a healthy connection to the router. Hence, I assume this must be a glitch/bug. I've been ignoring the "poor" report and devices are communicating just fine w/ Satellite #2. Just thought I'd pass along...
Try moving the RBS closer to the RBR.
Try swapping RBS with each other to see if status changes or moves with RBS.
Did you power OFF the Orbi system for 1 minute then back ON after FW was updated?
Quaksyx wrote:
I've been using this firmware for several weeks and largely believe experience has been good. I do believe there's a bug, however, in the web interface. It regularly reports one of my satellites with a "poor" backhaul status:
Things always showed "good" under previous firmwares and I didn't move the locations of my Orbi devices. When I view the system via my phone app, it reports all "good". Additionally, when I power-cycle my system, I receive the blue light on satellite #2 indicating a healthy connection to the router. Hence, I assume this must be a glitch/bug. I've been ignoring the "poor" report and devices are communicating just fine w/ Satellite #2. Just thought I'd pass along...
I certainly did power off/on as suggested. Additionally, I finally factory reset router and satellites and set up from scratch, which didn't alleviate the "poor" back haul status issue. I will point out that if I hover on the config page it will intermittently also read "good" on Satellite #2 (and flip back to "poor" after hovering longer). Perhaps I will try moving the units, however, I will say that I have Ring cameras outside the home and under previous firmware one of the cameras would frequently report a weak internet signal; with this firmware I've had no issues with Ring, which is an improvement.
Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
I've continued to struggle with a "Poor" backhaul status. I have moved the position of my 2nd satellite which did improve the status to "Good", however, this actually started causing problems for one of my Ring cameras, which then would report low wifi signal strength persistently. My router is in my basement, one satellite on my 1st story, and one satellite on my 2nd story of my home. I finally moved Sat #2 further away from the Router (and closer to the problematic camera) -- this resulted, Sat #2 connecting to Sat #1 in a daisychain topology (which is logical) and all reported "good" and worked good. Within the last couple days, however, Sat#2 has reverted to connecting to the Router rather than Sat#1 and it's back to a "poor" backhaul state. Despite multiple reboots, my Orbi system does not want to assume the daisychain topology. Is there a way to force? It's odd behavior that Sat #2 will elect to connect to the router directly then report "poor" backhaul when it's more than twice distance as compared to the Sat #1.
It should be noted that all of this is following a factory reset, recreating config from scratch, and most recently even attempted to regenerate the backhaul password (which didn't help).
When I observed an entire Orbi system restarting, it appeared (to me) that
- The router begins broadcasting WiFi signals first, including the user facing SSIDs and the "backhaul" SSID.
- Some time after the router begins broadcasting, the satellites (I have three) then begin broadcasting the user facing SSIDs.
My conclusion is that restarting the router may cause all of the satellites to notice the router backhaul SSID before they become aware of other satellites. If is well-known that devices that are designed to be "not mobile" often cease looking for a better WiFi connection after they have found one. (Whereas devices that are designed to be mobile, such as phones, tablets, and laptops, continue to survey the available WiFi networks looking for a "better" connection.)
What happens if the satellite that needs to be Daisy Chained is powered off and then powered back on?
(while the remainder of the network is operating)??
- I actually tried this as well (and forgot to mention). While the router and Sat#1 are up and running, I’ve rebooted Sat#2 by power cycling. It will oddly reconnect back to the router directly. Also interesting, the satellite will show a blue light, suggesting that the backhaul/connection is good. I’m still wondering if the current firmware has a bug in this regard. Devices do seem to work fine when communicating to Sat#2 despite the “poor” backhaul report of Orbi’s web diagnostics.
