NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi firmware update v2.1.4.16 availability
We’ve been monitoring issues that some customers have experienced in OrbiOS 2.1.4. In response, we’re releasing firmware that provides a permanent fix for the homekit issue along with various other f...
I got wired back haul working my friends system:
Can try this if you like.
Any network swtiches in the mix? If so, what the Mfr and model of the switch?
Zdman wrote:
Came back here after a few weeks to see if there were any good updates. Sadly no fw updates so I still cannot use wired backhaul and QOS just seems to do nothing. I really hate to ditch an expensive router and 3 satellites and start over, but I am fast approaching that point. I am also updating my Amazon reviews and suggest anyone else who feels ditched by netgear do the same. By the way, I do realize that for many people this product works fine. It worked fine for me with on Router and one wireless satellite, but for complex setups, this expensive system just does not cut it.
There has been lots of discussion in this forum about wired backhaul. Since March 2018, when I first obtained my RBK50 Orbis (operating in AP mode), I have been successfull with a wired backhaul.
However a few days ago, after installing an Edgerouter X, wireless backhaul worked, but I couldn’t get a wired backhaul up and running for love nor money, despite a lengthy period of dogged determination.
But I got it in the end, so now I have a tip that I think might be the answer for those also having wired backhaul problems.
Initially, the satellite in wireless mode, is harvesting nearby devices, which takes time. After several frustrating failed attempts I lost interest for a couple of hours, and then, I decided to try again and it just worked. No coloured ovals, straight in.
The experience is reminiscent of a learning mode, but in reality, I think the device harvesting routine dislikes being interrupted.
I don’t have any other explanation about why establishing a wired backhaul failed at first, but after an hour or two it worked instantly.
Worth a try?
Hi,
I replaced my Netgear R7000 with Orbi RBK50. I set them up as AP. Previously, with my R7000, I can easily achieved my Wired LAN speed up to 900Mbps. However, with Orbi RBK50, I can only achieved my Wired LAN speed up to 90Mbps.
What could be the issue?
Thanks
manikam Try enabling WMM ... makes a tremendous difference in speed.
And to confirm a previous suggestion:
Setting WiFi to a specific channel rather than AUTO has also made the connections more reliable - not perfect, but far more consistent.My Setup is ISP Fibre Connect modem -> DLink 865L (dhcp, WIFI disabled) -> Wired LAN to Orbi RBK50 -> Wired Lan PC
With NetGear R7000, my PC speedtest can achieved 900Mbps, with Orbi RBK50 only 90Mbps.
cheshbr wrote:
There has been lots of discussion in this forum about wired backhaul. Since March 2018, when I first obtained my RBK50 Orbis (operating in AP mode), I have been successfull with a wired backhaul.
However a few days ago, after installing an Edgerouter X, wireless backhaul worked, but I couldn’t get a wired backhaul up and running for love nor money, despite a lengthy period of dogged determination.
But I got it in the end, so now I have a tip that I think might be the answer for those also having wired backhaul problems.
Initially, the satellite in wireless mode, is harvesting nearby devices, which takes time. After several frustrating failed attempts I lost interest for a couple of hours, and then, I decided to try again and it just worked. No coloured ovals, straight in.
The experience is reminiscent of a learning mode, but in reality, I think the device harvesting routine dislikes being interrupted.
I don’t have any other explanation about why establishing a wired backhaul failed at first, but after an hour or two it worked instantly.
Worth a try?
The "learning mode" you're referring to is called a broadcast storm, and results from the router considering both the wired and wireless interfaces active with the same address at the same time.
The solution is a very basic tenet of networking called STP (Spanning Tree Protocol), designed to prevent this very issue, but apparently one Netgear hasn't heard of. (This has been proven by at least two people manually enabling STP on the router temporarily via telnet.) I had small hope Netgear would eventually turn STP on by default, but given there hasn't been a new beta firmware (or even any signs of life) out of engineering in quite a while, I rather doubt it now.
