NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi Firmware 2.3.1.48 Breaks Daisy Chain Functionality
Previously excellent daisy chain backhaul from one RBS50 to an RBS20 was rendered nonfunctional by the updated firmware, from*44 to the latest *48.
Correct steps were followed in the firmware update process, gear was power cycled, distant rbs20 was later restarted after rbr50 and rbs50’s were up and running, and rbs20 would still only connect to router.
Solution was to rollback all firmware to *44. This allowed again for excellent daisy chain connection for the backhaul from rbs50 to rbs20.
Short story - don’t use firmware *48 if you make use of the otherwise excellent daisy chain backhaul functionality.
Correct steps were followed in the firmware update process, gear was power cycled, distant rbs20 was later restarted after rbr50 and rbs50’s were up and running, and rbs20 would still only connect to router.
Solution was to rollback all firmware to *44. This allowed again for excellent daisy chain connection for the backhaul from rbs50 to rbs20.
Short story - don’t use firmware *48 if you make use of the otherwise excellent daisy chain backhaul functionality.
6 Replies
- I’m not having problems with daisy chain on .48. Orbi plus two satellites. Have you tried a totally clean reinstall after resetting to factory setting on all satellites and Orbi?
RBR40 to 2 x RBS20 and one RBS30W
Took about 5 minutes for daisy-chained Satellites to find each other, but they did, and no issues so far
Try giving more time to the setup and process.
Try a factory reset and setup from scratch.
Others are working with v48 FW.
- I appreciate the above replies, and also tried all the steps offered as possible solutions prior to rolling back firmware to *.44 and nothing short of the firmware rollback worked.
Perhaps there is something specific about using an RBR50 to RBS50 with daisy chain backhaul to RBS20 that doesn’t work in my particular configuration with *.48.Well the RBS20 is a lower connection rated satellite where the 50 series rates at 1700Mb on it's wireless back haul. The 20 series come in at 868Mb. Not sure if this would effect how daisy chain works or not. Would have to find another RBS50 to test it out. Even though 20 and 50 series are supported, it's best to keep the same rating satellites for best operation.
gassynizz wrote:
...
Correct steps were followed in the firmware update process, gear was power cycled, distant rbs20 was later restarted after rbr50 and rbs50’s were up and running, and rbs20 would still only connect to router.
...If Daisy-Chain is enabled on the Router and not enabled on the Satellite, it might explain this behavior. Points your browser to Satellite-IP-Address/debug.htm and check its daisy chain status. There should be a grey check box next to it.
If the box is not ticked, try these:
1. telnet into the Satellite
2. config default
3. config commit
4. reboot
That will instruct the Satellite to refresh its Daisy-Chain setting along with all other settings from the main Orbi Router.
