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...
Reason for asking for Mfr and Model# of swtiches is to help identify if switches being use are managed or non manged. There have been others reporting problems with Managed switches with Orbi systems. Also have users reporting no problems with non managed switches. Some users don't know how to identify what they have so I ask so I can help them figure that out. One user reported that disabling IGMP protocols on the Managed switch helped him so I've been passing this along as well. Were not data collecting, just trying to help troubleshoot issues seen with managed switches. So asking for switch information isn't a security issue. Valid troubleshooting step is all.
Users using manages switches should take them out of the mixed while trouble shooting wired back haul issues. Compaire with non managed swiches if one is available. Try disabling IGMP protcols. If this still fails to fix wired back haul problems, you'll need to contact NG support and let them know.
I 've had ZERO issues with wired back haul while using two non managed switches on my network with the Orbi system I have.
I have a non managed Cisco SG100-16 16-Port Gigabit Switch (SG100-16-NA). My Ethernet backhaul was working fine on 2.1.2.18 but since then every auto upgrade kills the entire network. I have 1 RBR50 router and 2 RBS50 satellites. All are beyond wifi backhaul range and require Ethernet to talk. When I run 2.1.2.18 with Ethernet backhaul my entire home has a clean mesh running. Every week now I need to reflash back to this old firmware to make sure my security system and all other internet based items can work. Ugh, painful.
Some have mentioned doing a factory reset and set up from scratch:
Whats your process after the FW has updated to most recent?
Usully a full reboot should work. I believe one user said to disconnect everything from the Orbi system accecpt for the satellite(s). Get the satellites working on wifi first, then connect the ethernet and let the one satellite re-configure, give 5 minutes. Top led should turn BLUE. Do same for 2nd satellite if you have one.
Some say to disable daisy chain on the router. You'll need to try this out enable or disabled to see what works. Disabled should work best.
If you can get ethernet backhaul working then re-connect all other LAN devices.
e1superman wrote:
I have a non managed Cisco SG100-16 16-Port Gigabit Switch (SG100-16-NA). My Ethernet backhaul was working fine on 2.1.2.18 but since then every auto upgrade kills the entire network. I have 1 RBR50 router and 2 RBS50 satellites. All are beyond wifi backhaul range and require Ethernet to talk. When I run 2.1.2.18 with Ethernet backhaul my entire home has a clean mesh running. Every week now I need to reflash back to this old firmware to make sure my security system and all other internet based items can work. Ugh, painful.- This is just Silly, sorry.
As I said, my units are beyond wifi range of each other. I can't do this every time power goes out or another FW is released (even if this works). This seems like a kitchen sink debug method.
Easy fix (for now). Allow us to turn off auto update.I agree, having to power up devices in specific sequence is un-realistic and so is the expectation to do a factory reset with every firmware update.
If Netgear feels that this is the solution after over 6 months of issue with wired network backhaul then the product needs to be recalled.