Orbi firmware update v2.1.4.16 availability

You're saying two satellites are given the same IP or that the router is handing out the same IP twice?  (The former could happen even in AP mode.)

What you're talking about is effectively the same thing, just that the two interfaces aren't on the same device, but STP would again prevent the entire network from crashing as a result, the second/duplicate device would simply be ignored with no storm.  That's how things are supposed to work.

Ikigai (MR2.2 Orbi Stability) I am one of the beta tester and with this i have no problem with rebooting, but it will lose internet connection occasionally but after some minutes it back again, and it also have unstable speed. Before this i had to reboot it each day (I use the backhaul)

What is the Mfr and model# of the IP modem?

What is the model# of the switch? 

What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
Try disabling the following and see:
Daisy Chain, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).

---

RossoScuderia wrote:

Been having some constant issues with the Netgear Orbi's. Finally with release 2.1.4.16, things got much more stable however in recent weeks we have had a decline of Internet stability. The house is fairly large (10K+ Sq Feet on one floor) so we were recommended Orbi's due to the wired backhaul feature. We are using 1 Orbi RBR50 and 3 RBS50's. They are all using Wired Backhaul and all using the latest 2.1.4.16 firmware. We are setup in AP Mode.

 

Here is how the system is currently setup using 4x Cox T1 Lines coming into the house.

 

• Cox / Overture Eithernet Over T1/E1 Switch
• Linksys Router/Modem (wifi turned off)
• Netgear 16-Port 10/100/1000 Mbps Gigabit Unmanaged Switch (connected directly via 
  Orbi RBR50 (In Far West Side Of House - Theater Orbi)
  • 1x RBS50 wired backhaul going directly from Satellite to Master Bedroom (Far East Side)
  • 2x RBS50's are connected directly from Netgear Switch to Satellite (Library) of which is on the very edge of being able to communicate via wifi to the Router but is wired to the switch, and the second one (Bedroom) is also wired directly to the switch

 

At this point, we have spent countless hours and are having tons of issues with it dropping/acting slow. yesterday i reboot'd the router and everything just went down. Spent about 3 hours trying to stabalize it by turning off and back on the satellite's 1 by 1, but still, seems like some rooms are not connecting via the wired backhaul connection.

 

The other issue we are seeing is that in between the Theater (Router) and Library (Orbi) is the kitchen where we spend most of our time, Its a giant dead spot. We have MEMO and FAST ROAMING unchecked.

 

I just dont get it. Everything has been replaced, everything has been rebooted or restored to factory default several times.

 

Can anyone give some guidance as to what we are doing wrong here????

---

after spending many hours troubleshooting and monitoring the performance in many various configuration and setups, my conclusion is that the main culprit is the satellite (RBS).  once connected with the satellite(RBS) whether via wireless or wired to the router(RBR), all hell break loose.  connectivity drop every few minutes.  least to mention the slow wifi bandwidth speed from both router(RBR) and satellite(RBS). 

i have a 1Gbps connection at home.  when connected via Ethernet LAN cable to the modem, i can get more than 700Mbps.  similarly when connected via Ethernet LAN cable to RBR, i can get about 650Mbps.  but when connected via wifi, the speed drop to a mere 50~70Mbps.

here is a screen shot of the connectivity drop.

You can give this a try:

https://kb.netgear.com/22688/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP

Use the TFTP program thats built into windows, do NOT use the on stated in the link. It doesn't work. The one built in with windows does. 

You'll need a LAN wired PC connected with the router. 

IF this fails, you'll need to contact NG support and ask for an RMA. 

I recommend doing any FW updates with a LAN wired PC connected to the router. 

DarrenM

Christian_R

---

bmelvin wrote:

I made the mistake of trusting your software over a wireless connection. The software reported that my Orbi router and satellite firmware (2.1.4.12) was out of date, and said 2.1.4.16 was available. I clicked Update All. I waited a couple of hours and the Orbi was still blinking white. Eventually I gave up, hoping that power-cycling would make something happen. Long story short, I'm able to connect to both satellites over Ethernet, and both were updated. The router is totally bricked. It won't boot, and won't be reset. I can't get an IP address for it, can't reach it at all. Sometimes, when I power-cycle it, the power LED is green. Sometimes it turns to flashing red. The top light continues to flash white, ad nauseum. What do????

---

End for me.

Orbi has really a problem, i think with DHCP, even in AP mode.

I resetted my ORBI, no satellite, switch in AP mode, connected to my internet box (Orange LiveBox 4 from France) and nothing else.

One day later, all my DHCP setting of my main router (Livebox) is gone.

It's not the first time, when i connect the orbi on my router, some time later some devices had bad IP (All the IP are static in the DHCP of my router).

Why orbi do something in AP mode !!! should just act like a switch !

There something wrong with orbi, it's a fact, it's a bad product, i can't use it again any more.

No need to hear "it works for other people bla bla bla", it should works with every body, without doing anything, plug and play, like all the device i use, orbi is really the worst device i had.

After loading v.16, did you do a factory reset and set up from scratch after loading that version of FW?

Others have mentioned that this needs to be done for using v.16 FW.

Also how is the placement of the satellites and how is it configured.

---

eepgmik wrote:
Unfortunately since installing this version my WiFi goes out every hour or so and takes 15-30 seconds to recover each time. I also still saw the router turn magenta and had to power cycle it. Overall the quality of the router got worse with this update and I’ve reverted to .14 with much better reliability.

---

Others have not mentioned seeing problems with this version of FW and rendering.

---

Cobenza wrote:

I was pointed at this thread from another about an issue where my device list is not rendering any devices. Does this solution fix my issue? I don't see it on the list.

---

Folks. Today I returned my Orbi RBK50 for a refund, and replaced it with Ubiquiti.  I already had an Edgerouter X, and today I added a single Unifi ceiling mounted access point.  

After championing Orbi for around 4 monthsbecause my system was stable, why am I pulling the plug?  One of the reasons I had stability was the hours I put into keeping it on track.  Lifx and  HomeKit needed the most support.  Mostly the issues involved attached devices migrating randomly between the router and the satellite, but two issues raised my ire the most.  The new beta firmware gave what appeared to be more accurate signal strength and link rates, or it could have been a bug weakening the sat, so I asked through the forum as a beta tester about the lack of release notes about this and other issues.  But Netgear did not respond, so that’s a black mark.  The other issue is the 90 day support, then you pay.  In Australia, our consumer laws give us 12 months warranty, so we don’t have to pay after 90 days.  I was advised that poor support is grounds for seeking a refund, too, so I did.  

Bye. It’s been fun