NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Strange Daisy Chain order on my RBK53 set
Hi, I had to re-position my Orbis to cover not only the full house area but also the garage and garden. The Orbi router and three satellites have arranged themselves for this order: The router (...
The satellites should self-regulate and connect to each other to provide the "strongest" signal. First, be certain all the satellites and the router have the EXACT same firmware installed. One of the current issues is the reporting of daisy chain connections tends to be "off", i.e., the satellites take a long time to settle and may change their connection reporting frequently. The smartphone app can also show a different status than the built-in browser GUI.
If you are getting "Poor" connections reported, I suggest you tell the router to remove all three satellites and power down the satellite. Then power the satellites up–one at a time–starting with the closest one. Then reconnect/resync that one. Allow it several minutes (15-20) to establish a "Good" reported connection. Then go to the next satellite in the chain and repeat until all three are back online and reporting "Good".
After allowing this "new" system at least 12 hours to settle, if the backhaul status stills shows "Poor" I suggest changing the location of the satellites to achieve a "Good" backhaul signal. Good luck!
No, you can't force certain satellites to connect it the order you want. They auto-negotiate based off signal strength.
You can optimize placement a bit more. They need at least 30 feet between router/satellites to properly negotiate setup.
You might also find that obstructions within the walls can cause signal degredation.things like hvac, plumbing, foil lined insulation all can block signals and what you might think is a "better" setup isn't based of where the router/satellite is setup. Try moving closer/further/laterally within its current setup. I moved my devices around for several weeks before I found the optimum solution. (plus I just like to optimize)
You can also try playing with disabling beamforming/mu-mimo/fast roaming to see if it'd help.