NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
What happened to my posting
I posted then edited the posting with a different title and it disappeared? https://community.netgear.com/t5/Orbi/Sat-WiFi-downloads-slow-to-kilobits-s-with-wired-backhaul/td-p/1789011 I spent a lo...
HTBruceM wrote:.......
I REALLY need some stability in the network because I'm planning to drop my Dish Network and switch to YouTube TV streaming service in the next month, so even TV viewing will then be dependent on internet access. Technically I don't even really need a mesh system because I've got the CAT6 wiring I need to just use APs. Whatever; this is where I am right now.
I have a very stable and robust wifi network currently with 2.3.5.30. All I needed to do related to wired backhaul is mentioned in this post: https://community.netgear.com/t5/Orbi/Wired-Backhaul-in-recent-firmware-releases/m-p/1783871#M67538
This should not e difficult to do to fix your issues and improve your system.
HTBruceM wrote:I spent a lot of time creating this post, I hope it isn't gone.
My guess is that it is indeed "gone". I, also, was typing a response only to have the forum pop up a message that the post I was replying to was "Missing" (or words to that effect).
If both satellites are connected with ethernet, there is no reason to enable Daisy Chain. The point of Daisy Chain is to allow a satellite to connect to the router through another satellite. If I remember correctly, enabling Daisy Chain also causes the Orbi satellites to create their own backhaul channel. Ordinarily, I would say "who cares? the Orbi comes out of the box with Daisy Chain enabled even when the purchase is an RBK50 with one router and only one satellite." My opinion is that Netgear thinks customers may purchase another satellite and be puzzled when it doesn't connect and not realize they may have to enable Daisy Chain.
You're probably right.
I wish they would figure out a way to DISABLE the backhaul radio channel (or repurpose it for another client interface) when wired backhaul is present. That would surely eliminate the broadcast storms, loops that they're trying to eliminate. The RBS50 appears to have only one MAC address - whether the backhaul is WiFi or wired - the same MAC address shows up in the Attached Devices. There must be a single MAC controller and some sort of hybrid dual PHY... which might be the reason that wired backhaul is so touchy. Maybe they've got a chicken/egg situation with the backhaul WiFi vs. wired. Probably initially comes up in WiFi mode after reset/powerup, then some sort of "magic sauce" is done to enable the wired backhaul later. Having the same MAC for both might be the source of all the backhaul weirdness. The hardware being what it is (can't change it), they're trying to make things work in FW.
Couple reasons for wanting to use ethernet backhaul.
1) the perceived stability and consistent bandwidth of wired ethernet vs. WiFi
2) I also feel some guilt for consuming 5GHZ channels in my neighborhood that I don't really need since I have the wiring available to setup a wired ethernet backhaul. It looks as if the backhaul radio is still enabled but I assume it isn't sending packets and therefore colliding with neighbors.
BTW attaching a screenshot of speedtest from Android phone showing the speed slowdown.
