OrbiOS 2.1.1

We have 3 ipads and 3 iphones.....no issues here.  Mac Mini is fine also, however it is wired. 

Didn’t have any issues with any Mac devices either. Worked perfectly with 3 Orbis wired. 

Nest cams are more stable under the Orbi 2.1.2.10 beta.  Where the problem lies, however, is the main router itself - I had random disconnects that killed the entire home network of 45 devices. Thus going back to Google Wifi. Will be trying Eero Pro 3 pack wired in coming days. 

DarrenM  Do you have any insights into the firmware file system and whether it includes something like kdump or linux-crashdump to grab kernel panic crash dumps?  I poked around via telnet and could not see anything on my end.  I looked at the sysctl.conf and such for any clues but alas...  It's going to be difficult for us to help diagnose on our end (and help your end fix these issues) without crash dump tools.

So after returning from church my desktop and my wife's laptop will not connect, nor will my iphone and ipad.  Had to power cycle the main Orbi.

Is there a stable release of the firmware that someone can recommend?

Try .074

---

lbdyck wrote:

So after returning from church my desktop and my wife's laptop will not connect, nor will my iphone and ipad.  Had to power cycle the main Orbi.

 

Is there a stable release of the firmware that someone can recommend? 

---

I'm still on the 2.1.1.16 release and after 2 solid weeks of uptime, the network just died. I plugged my PC into the modem and was able to get back online, so it's not my ISP. But now my network is dead.

Nor can I log into the web interface or the debug page on the router either. I repowered the RBR50 and no change. 

Edit: So as I was digging out my old router and AP so I could get my network back up, I hear my PC chime for an inbound message. Sure enough, the Orbi is back online. But it took a good 10-15 minutes for it to come back up.

I cut my teeth in the home wifi world on a DLink DI-624 and was always trying to find a new firmware to make that thing work better! I'm not inclined to repeat that ordeal.

I confess to being perplexed what to do. I'm very, very tempted to unplug this thing, pack it up, and take it back to Costco and put my old system back in place while I research my next option.

You might try the beta - I'm running it now and it's working well.

I’m using the beta and it is not as stable as 074

2.1.2.10 Beta reset after 7 hours. No improvmement for me.
Also still has the problem with the Galaxy S6 too.

I have had a pretty mixed experience with my Orbi RBR50 and 1 satellite over the past year or so that I have owned them with the big issues being random device disconnects and instability. I have thus pursued firmware updates vigorously to try to make this a device I can brag about as I have with other Netgear items in the past. I really want these to work as Orbi's inclusion of enough ethernet ports on the router is the weakness on all other units that prevents me from jumping ship. I also like the Netgear web interface though their iOS app is trash.

Firmware wise, I moved from 2.1.1.16 to 2.1.2.10 18 hours ago. Following that, I have yet to experience a router or satellite reboot (though admittedly this was happening only about every 8 days or so before) and I have yet to find a device disconnected which happened a couple times under 2.1.1.16 on a once a day sort of interval.

I will say my most stable version was 2.0.0.76 which is a version I kept here as a backup should future builds continue to offer problems since .76 included the Krack Wi-Fi fix.

A few more notes about 2.1.2.10

* I have about 28 device attached and more of them are connecting on 5G than has been the case in the past - I prefer 5G to 2.4 for speed and reduced the 2.4 power level to 50 percent to hopefully encourage 5G connections over 2.4.

* I have a few devices which I am anticipate are really connected to the satellite or router but are reporting the opposite so the mappings still look a littel suspicious to me or there are some real distatnce linkages happening for me (my implicit beamforming is off as is MIMO)

* My Ring Pro doorbells are seemingly getting solid 5G connections which was not always the case

* My router and satellite CPU usage still seems high to me at between 15 and 30% with not real heavy use but who knows what normal should be on this anyway. At least I have not seen over 45% in recent times.

* My only Android devices are some Amazon Echo Shows so can't help much with the Android concerns

* I did see some oddities happening over on the Linksys Vellop list as well. It makes me wonder if the Qualcomm chipset isn't part of the problem here.

* I am glad Netgear is still chugging along on this but I wish I had a greater sense that some real experts were behind the developments--it looks almost like a hobbiest development team given all the random problems that keep surfacing. I don't mind this on betas and I don't want to complain about betas as we need to try to help them figur this out but so many main release builds have giant problems that it just make sme wonder what is happening and where in the world the development is happening for Netgear.

If any of the other manufacturers released a mesh system with 4 or more ports on the main router I'd jump ship for that but until then, I'll stick with Netgear and hope it gets better soon.

Okay, I've been up on the beta for a day and six hours at this point.  I was having horrible disconnect problems, enough to switch to Eero, but I put the Orbi's back in now because I wanted to try the beta, and hopefully it would fix things and I could save $500.

Right now all seems good.

The difference right now is that before I had all ports filled on the router AND satellite.  Right now I only have a printer on the router, and my Hue hub on the sat.  I'm wondering if that plays into anything at all.

For those of you who have tons of stuff jacked in and a lot of disconnects, I'd be curious to see if uptime goes up if you remove most of those.  It's not ideal AT ALL, I know, but for me I can live with it if that makes things stable.  Maybe the internal switch is part of the issue?

Good luck all,

Grey

I'm running the Orbi as a router with two satellites attached with wireless backhaul - one one satellite I have plugged into ethernet my TV, an AppleTV 4K, Sound bar, and Xbox1X. No issues - of course I don't have any switches plugged into my Orbis. The Router has the Shaw cable modem in bridge mode, a Synology NAS, a Chaimberlan garage door hub, with one spare port. Upstairs I have a satellites in a den that connects a laptop when someone's working from there. No stability issues with those things plugged in. Tons of other things attached through Wifi - Ring Doorbells, Cameras around the house, Wemo devices, Wifi lights, iPhones, iPads, for a total of 24 devices on at all times going up to about 35-40 devices when everything is on.

Thanks for sharing. Sounds like it’s stable for you.  Three unit wired orbi with latest beta 2.1.2.10 was stable but suddenly it rebooted for no reason. Nothing changed so it’s hard to explain the sudden reboot. 

The iOS app is stable but not up to par. With 45 devices, there’s no way in the app to list the devices in a table (must go through the web to get) and no way of knowing to which satellite devices as connected through the app. Not a polished app in my view. 

The instability of the Orbi forced a switch back to Google Wifi, and soon to test out Eero Pro 3 unit wired. Loved the orbi (wired) until it rebooted itself without reason, and again and again. 

Best of success. Hope it stays stable for you aaz

how many of you guys did a factory reset?

and how many of you are doing MORE than a factory reset? 

and if so, what all are you doing to try to set these things back to a "default" state?

---

larryindublin wrote:
Until I am told by Netgear that I need to do anything more than just install a firmware update "as is", I don't think I should have to experiment.

---

i agree on the experimenting part!

but seeing how it feels like i was sold a half baked net gear experiment, i was looking to see what others have tried. 

not sure anyone else noticed, they are busy building LED control into the firmware instead of fixing stability issues

---

aaz wrote:

You might try the beta - I'm running it now and it's working well.

---

I don't know. I had no issues with 2.1.1.16 for 2 solid weeks (other than device reporting) and then it just died. No power spikes, surges, or anything. And I have it on a UPS anyway. 

I could not get the web interface up or the debug page. Everything was dead. So after I piddled a while trying to fix it, called my ISP to check on network outages, connected my PC directly to the modem so I could get back online, and finally was dragging out my old gear to get my network back up, the Orbi came back to life.

That sounds more hardware than software, I'm thinking.

Right now I'm back on my old gear while I ponder my options.

---

Blcklab wrote:
What are the disadvantages of 1.11.0.20? .74 has been pretty stable bit even .74 resets wifi connections

---

It doesn't address the Krack vulnerability, iirc.

Anyone already poked at the telnet access, which you can acticate on the debug page? I poked around a bit and found that, although the devices list is totally borked on my setup, the bridges pretty much tell me that the wireless devices are located on the device router/sat on which one would expect them to be.

I don't know, why the UI doesn't grasp that, but it seems to be only a minor issue, which should be easy to fix

I have put the two of my Orbi devices under tight surveillance by my network monitoring, should either of them fall of the net, it will be noted.

I finally fixed my problem with my orbi, very easy... I returned it to the store and got a velop linkys kit, this thing is rock solid. Good luck all

I have been having continued intermittent reboots over the last day or two since a manual update to V2.1.2.10

Orbi is in AP mode connected to an Asus router, also connected to the router is a Fingbox.

The Fing is reporting the Orbi having a MAC ending XX:XX:A5 and being connected to the network with no problems.

Then Fing then reports the Orbi as being "in range" and the network seems to degrade.

Followed by Left the network.

Shortly after it re enters the network.

But, at the same time, R50 enters the network on the same IP but with MAC XX:XX:A6 (only the last digit differs)

Both MAC's then leave the network and the Orbi setup crashes/reboots.

The timeline might not be exact and am unsure how accurate the Fingbox is.

I am trying to work out why the Orbi would be connecting with the MAC variation - changing from A5 to A6 ? or is this considered acceptable from a device with multiple MAC's

Certainly if the reboots continue I will revert to .74