NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
pbarham
May 09, 2020Apprentice
Spanning Tree problem with Orbi RBR50
I have been having network problems with my Orbi system for a few months now.. The symptoms are similar to issues others have reported, where satellites and other devices gradually disappear from th...
mdsteele47
Sep 24, 2020Aspirant
We appear to be experiencing a very similar problem with a Philips 272P7VU monitor that has a USB-C hub with an Ethernet jack. Can't quite isolate what the behavior is with the monitor that is causing the dropouts, but it is similarly killing every wired connection in on the RBR50 (which has a network switch attached to it).
Has anyone found a fix for this within the Orbi? I appreciated the link explaining the Ethernet Pause Frame but that didn't seem to point to a fix.
mdsteele47 wrote:... Philips 272P7VU monitor that has a USB-C hub with an Ethernet jack. ... with the monitor that is causing the dropouts, but it is similarly killing every wired connection in on the RBR50 (which has a network switch attached to it).
For the moment there is no other option but disconnecting these hubs in direct connection with the network switches (e.g. the built-in on Orbi). The problem is that the Ethernet Pause Frame is intended to remain on the singe physical link (e.g. Orbi <-> Switch, Switch <-> Computer) only. Why ever, Ethernet Pause Frame is by error (switch chip embedded firmware) forwarded to other physical link where it can will stop that next port(s).
mdsteele47 wrote:Has anyone found a fix for this within the Orbi?
Nothing we can do from the user side for now - except to wait for an Orbi firmware update which does include and updated switch firmware (hopefully loadable by the host) and/or direct "host" ports are handling the Ethernet Pause Frame appropriately.
Piling on here. I am experiencing the same issue with different Orbi hardware and USB hub. I have an Orbi CBR40, and have two different USB hubs with gigabit ethernet ports (OWC Thunderbolt 3 Dock, and VAVA USB C Hub). When I have an ethernet cable plugged into either or both of the hubs, I experience the same issue described here. After 15 mins or so, every device on the wired network looses connection, yet the wifi network is unaffected. Restarting the Orbi fixes the issue temporarily only. When I remove the USB hubs from the equation there is no problem with the wired network. This is incredibly frustrating. The behavior described by pbarham and also in the Pause Frame article match my experience.
I am running the latest firmware for the device V2.5.0.14_1.0.8. No previous firmware updates have improved or fixed this behavior.
Is there any update on a coming fix from Netgear to address this, or has anyone found a workaround?
Something to contact the Mfr of these USB hubs about. If these are the only devices that don't work with Orbi, then you'll need to find help and information from the Mfr of these devices or find something that works. I have used small USBC to Ethernet adapters and these work for Orbi. Hubs seems to be a different animal and cause problems for Orbi systems.
RyanSpohn wrote:Piling on here. I am experiencing the same issue with different Orbi hardware and USB hub. I have an Orbi CBR40, and have two different USB hubs with gigabit ethernet ports (OWC Thunderbolt 3 Dock, and VAVA USB C Hub). When I have an ethernet cable plugged into either or both of the hubs, I experience the same issue described here. After 15 mins or so, every device on the wired network looses connection, yet the wifi network is unaffected. Restarting the Orbi fixes the issue temporarily only. When I remove the USB hubs from the equation there is no problem with the wired network. This is incredibly frustrating. The behavior described by pbarham and also in the Pause Frame article match my experience.
I am running the latest firmware for the device V2.5.0.14_1.0.8. No previous firmware updates have improved or fixed this behavior.
Is there any update on a coming fix from Netgear to address this, or has anyone found a workaround?