NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OrbiOS MR 2.1 issues
I wanted to reach out to provide a quick update on OrbiOS 2.1 software. We believe that these issues are affecting some users. Rest assured that we've been following this issue and working hard beh...
I’ve had the 2.1.3 Beta running for a few days now. 1 base, 2 satellites, 21 devices, no dropped connections, everything talking fine now. Yeah. Thx.
As FURRYe38 and Orbi2018-3-3 have stated, many people have had good luck with it, myself included :-)
2.1.3.4 firwmare is still buggy for me as connecting the ethernet backhaul bricked my entire network. Beta 2.2 fixed the issue.
I'm using v2.1.3.x here wired back haul working 4 days +. No issues. Using two NON Managed swiches in between the Satellite and router.
One thing i found to work best for set up initially. Set up the satellite via wireless first. Then connect the ethernet cable from the router to the satellite. Give at least 5 minutes for the system to reconfigure itself and settle down. If you have a 2nd satellite, do the same time, sync wireless first then connect ethernet cable and give 5 minutes.
Again, managed switches will cause problems with the orbi system. NON Managed switches are preferred. If your having problems with managed or non managed switches in between the router and satellite, please give Mfr and model # information for switches so we can forward this to NG support. Also give details on if Daisy Chain was enabled or not while using switches.
ppilot212wrote:2.1.3.4 firwmare is still buggy for me as connecting the ethernet backhaul bricked my entire network. Beta 2.2 fixed the issue.
RBK53, FW 2.1.3.4
D-Link DGS-1024D (unmanaged 24 port) between router and sats. One "management" PC is connected directly to router port.
FIOS ethernet 100/100.
Daisy-chain is ENABLED (by default)
Major ethernet backhaul issues. Sats either no connect or solid magenta. They may appear in DEVICE list as WiFi connection, instead of under the SAT list as ethernet connection - when they do appear at all. While this is going on, router goes off into the weeds - intermittent ping replies and no internet/WAN connection. Unit gets very warm to the touch, a LOT more than when operating normally with 5Ghz WiFi backhaul. I have tried power cycles (incl on the switch), sync buttons, hard RESET on sats, waiting for 10 minutes after each attempt. No go. What is so frustrating is that you are "in the dark" most of the time; your only clues are the lights and the management UI - but even that goes down when the "internet" connection is not working. You never know how long is long enough to "wait" for something to happen. It would be nice if the router would at least maintain its ethernet/WAN connections while backhaul synchronization is occurring.
It would seem like a straightforward feature to implement a backhaul radio ON/OFF button somewhere in the Sat's UI. I know that could be like sawing off the branch you're standing on... but you could always return to backhaul radio ON with a hard reset. It seems like that should be a decent solution to work around some of the issues with reconfiguring for redundant backhaul. Hopefully they don't have the same MAC address for the WiFi backhaul vs. the ethernet backhaul...
Like many others, I'm still in my product return window. Costco. Still keeping my options open.
My prior setup was a pair of Asus RT-AC66u with Merlin FW (one in AP mode, the other in router mode). My only real complaints were:
1) having to setup two nearly identical GUIs and update FW twice,
2) the impending "EOL" of the Merlin FW for my model, and
3) lack of support for their new AI-Mesh FW.
Where did you get the Beta 2.2 firmware from? I tried 2.1.3.4 and I am still having lots of ethernet backhaul issues. I originally had a managed switch that everything was connected to but after reading that using a managed switch could cause issues I went out and bought a Netgear unmanaged switch. Still no go. Did a hard reset of all the orbi's and 1 connected successfully and the other refused to connect via ethernet. During configuration the whole network was unusable... i'm positive it was something to do with the Orbi's configuring itself, but I can't can't think what it could possibly be doing to cause such problems. I'm thinking of returning the Orbi and going Ubiquiti APs since I'm using ethernet backhaul anyway if I can't get this resolved soon. :smileyfrustrated:
