NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi MR 2.1 Update 3/23/18
Our teams are still working through the issues, but I wanted to provide a quick update on OrbiOS 2.1. We usually wait to release our software until it's available across all Orbi product lines, but ...
Not really, you maybe already hitting the limits of your wifi devices. Just because they can connect at 866Mb doesn't mean the data can flow that fast as well. Doesn't work like that. Connection rates differ from data flow rates. The Connection rates are just connection rate speeds between the devices and wireless AP/router only. Mfrs have different designes and depending on chips used and implemented, data rates will differ and some are limited by the chips they use or implement. Honestly, is 866Mb data rate really needed on a phone, stop and think, what are you doing one thing at a time on ap phone that would need that kind of bandwidth? FB? text? voice? Nothing on a phone needs that kind of data rate. Streaming compressed video even doesn't need that kind of data rate. Theres many connection however on phones, apps and browsers and all this combine needs some bandwidth. That were the connection rate comes in. Wider connetion rate, more app, video and browser data can share the pipe.
My current v2.1.3.x FW has working wired back haul. Zero issues so far.
turns2stone wrote:What are the chances that an upcoming 2.2.x firmware will improve wired backhaul? Because I cannot get this to work, unless the satellites are directly connected to the Orbi router. And my switch/cabling in between the router/satellites has never caused any problems in the past 5 years.
Maybe an even more important question: how much improvement have you guys seen going from RBR50->RBS50 Wi-Fi backhaul performance to wired? My Orbis are max 40 feet from each other. Most of my iPhones/iPads/laptops have up to 866Mbps antennas/performance. I can easily get 300-500Mbps (I do have 1Gbps internet service). Going from the 1733Mbps (real world 800Mbps throughput max?) backhaul, to wired Cat6, is it realistic to expect 400-600Mbps Wi-Fi performance on devices that support 866Mbps?
FURRYe38 wrote:Not really, you maybe already hitting the limits of your wifi devices. Just because they can connect at 866Mb doesn't mean the data can flow that fast as well. Doesn't work like that. Connection rates differ from data flow rates. The Connection rates are just connection rate speeds between the devices and wireless AP/router only. Mfrs have different designes and depending on chips used and implemented, data rates will differ and some are limited by the chips they use or implement. Honestly, is 866Mb data rate really needed on a phone, stop and think, what are you doing one thing at a time on ap phone that would need that kind of bandwidth? FB? text? voice? Nothing on a phone needs that kind of data rate. Streaming compressed video even doesn't need that kind of data rate. Theres many connection however on phones, apps and browsers and all this combine needs some bandwidth. That were the connection rate comes in. Wider connetion rate, more app, video and browser data can share the pipe.
My current v2.1.3.x FW has working wired back haul. Zero issues so far.
All fair points and I understand about theoretical maximums and other factors. I guess I'm more interested in getting wired backhaul to work because I spend a fair amount of effort putting an Ethernet drop to my satellite locations. Also, I'm just trying to achieve the most consistent performance possible, which I assume Ethernet backhaul would provide.
Considering that I can get a satellite to connect via Ethernet backhaul when directly connected to the LAN ports on the RBR50, do you have any final tips for getting it to work before I give up for a while? I've tried establishing the connection directly to the RBR50, then powering off the RBS50 and moving to its real home, but no luck. I've tried (I think) every combination of power cycling the RBS50 with/without the Ethernet cable plugged in.