NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
itGeeks
Sep 26, 2016Apprentice
Feature Request: Orbi Satellite Ethernet Backhaul
As good as Orbi looks on paper I don't understand Y you would cut yourself so short and not support Eithernet backhaul for the satellites, I have 5 locations needing a system like this but without su...
- Apr 26, 2017
Let me acknowledge that our customer base has been clamoring for this feature for a while, and we are trying to be responsive to their needs. To provide context on why it's taking a while to get it out, during the first quarter, the Orbi Engineering team was focused on bringing out the two new products (RBK30 & RBK40) to market. Now that it's accomplished, we're actively working on bringing this feature and a couple of other interesting, market-requested features to you.
Orbi Product Team
truepudding
Oct 18, 2017Star
Great post ...
> The primary feature of mesh is the INDEPENDENT WIRELESS backhaul not grabbing ressoureces of the client networks.
but I disagree here. You described mesh in your post well, however (Instant roaming). Resources off the client network is nothing in a world of GB routers for $10. The physics between copper and wireless is mind boggling. This is the primary feature of ORBI, not MESH.
The mesh network devices job is to provide instant roaming to clients. đ How it provides that service differs between Orbi, and every single other comparible product that does support wired backhaul. Having a dedicated radio is awesome... but it lacks a feature that would make it the same as the competitors, plus the 20% better. That would make me buy it again.
Also keep in mind you are on a thread with dozens of people wanting this feature. So I donât think anyone wants to hear that not having this capability is a âfeatureâ. đ
> The primary feature of mesh is the INDEPENDENT WIRELESS backhaul not grabbing ressoureces of the client networks.
but I disagree here. You described mesh in your post well, however (Instant roaming). Resources off the client network is nothing in a world of GB routers for $10. The physics between copper and wireless is mind boggling. This is the primary feature of ORBI, not MESH.
The mesh network devices job is to provide instant roaming to clients. đ How it provides that service differs between Orbi, and every single other comparible product that does support wired backhaul. Having a dedicated radio is awesome... but it lacks a feature that would make it the same as the competitors, plus the 20% better. That would make me buy it again.
Also keep in mind you are on a thread with dozens of people wanting this feature. So I donât think anyone wants to hear that not having this capability is a âfeatureâ. đ
OrbiPhilip
Oct 19, 2017Luminary
The arguments against wired backhaul are amazing. If the ONLY reason to buy Orbi is the wireless backhaul, the design/engineering team has failed spectacularly.
Backhaul is backhaul. It's not a feature, it's a neccessity. Without it, the remote AP is a table decoration. When available, wired bachkaul should always be preferred for reliability. When it is not available, use wireless to overcome environmental limitation.
As for Netgear not publishing a roadmap, that's very short sighted to the point of working directly against their marketing efforts instead of complementing them.
- Dan_HOct 19, 2017ApprenticeSo they failed because they provided a product that works extremely well when you can't run wire? They failed because they didn't add wired backhaul for the 25 people bad at math who can't figure out wired orbis are a bad value proposition because if you can run wire they should be buying something much cheaper that would perform the same? Anyway it is coming eventually, so the point is moot. You'll eventually get something that was never advertised to begin with and hopefully you'll be happy.
- SandspikeOct 19, 2017Star
I don't think they've failed, but you are wrong. A mesh system that allows for seemless handoff under one SSID and management layer via wired backhaul is what we want. You can't accomplish that with a cheaper solution. If Netgear said, we can't/won't do that, then we could move on. But their solution with wired backhaul would be the best solution for most.
- Dan_HOct 19, 2017ApprenticeSo you are saying no one makes APs that handle single SSIDs that allow client roaming managed under a single pane?
BTW your device decides when to roam (not the Orbi) and with the Orbi you are either connected to the satellite or router. They talk wirelessly to each other and that is what makes them mesh.
- OrbiPhilipOct 19, 2017Luminary
Dan_H wrote:
So they failed because they provided a product that works extremely well when you can't run wire? They failed because they didn't add wired backhaul for the 25 people bad at math who can't figure out wired orbis are a bad value proposition because if you can run wire they should be buying something much cheaper that would perform the same? Anyway it is coming eventually, so the point is moot. You'll eventually get something that was never advertised to begin with and hopefully you'll be happy.Snark is not an adequate substitute for reading and responding to the substance of a post.
- hulster8valveOct 19, 2017Tutor
OrbiPhilip wrote:The arguments against wired backhaul are amazing. If the ONLY reason to buy Orbi is the wireless backhaul, the design/engineering team has failed spectacularly.
Sorry - your are not right. This product is designed for wireless backhaul and Mesh. There is a lot of other Netgear stuff you can buy if you just need wired backhaul and some wireless AP. If you just bougth for design reason - ok - that might be your prob.
I am on telling if your reason is single SSID and fast roaming there are other options.
So tell me why Orbi must have wired backhaul and there is no alternative for you.
Maybe I have overlooked something.
- OrbiPhilipOct 19, 2017Luminary
hulster8valve wrote:So tell me why Orbi must have wired backhaul and there is no alternative for you. Maybe I have overlooked something.
That is not the statement I made. Re-read it again.