NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
packetwerks
Apr 02, 2018Star
V2.1.3.4 Bridging
Starting a new thread specific to my issue. So I woke up this morning to V2.1.3.4 being installed. Not only was my wireless network down but so was my wired network. Started troublshooting and notice...
packetwerks
Apr 04, 2018Star
I had the latest version prior to v2.1.3.4 as it automatically upgraded. Whatever that was.
I'm not going to revert back a rev to troubleshoot this more -- this is now NETGEAR's problem. Someone from NETGEAR can easliy figure it out by looking at their source code repo to see if STP was enabled on the bridge interface (br0) prior to 2.1.3.4. I'm (obviously) willing to tinker and help but I think I've done enough. Surely NETGEAR has a testing lab where they can do this in minutes.
My only hope is that this issue somehow floats up from the community message boards to a devloper who knows exactly what I'm talking about here. The fact that an ethernet backhaul loop is trashing customer's networks because STP was seemingly left off is a pretty bad screwup. This type of issue isn't something your front-line support folks are going to be able to effectively troubleshoot. If you are a NETGEAR employee reading this, pop this thread into Slack and ask a dev to take a peek at this.
STP might have been disabled for some other reason that I'm not aware of - I don't have all of NETGEAR's use cases but this sure seems like a bad bug. There is a Reddit thread here: https://www.reddit.com/r/orbi/comments/88zy2y/v2134_and_ethernet_backhaul/ and other people are impacted by this.
FURRYe38
Apr 04, 2018Guru - Experienced User
- packetwerksApr 04, 2018Star
Done