NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
Yeah I factory reset the router via the web interface first. Then reset each satellite via the pinhole. Physically resynced each.
Satellite----cat5----Switch----Orbi Router----Wireless Clients
/|
Satellite----/ |
Switch-----VMware Server---Firewall----internet
|
|
Other hardwired stuff (e.g. AppleTV, etc.)Notes: Switches are D-Link DSG-1100-16/24 with default, unmanaged configs. ISP Cat5 goes right into firewall. No modem.
Firewall is a VMware-based Sophos XG appliance. It does DHCP and has not been changed in a long time. Not doing any fancy IPS or any other strange things to internal traffic. It's basically a "dumb" router at this point.
Not sure what you mean by "physically have the Satellites piggy backing of each other" I have both satellites connected to the same ethernet switch so that they can setup the bridge between them -- it was working in the previous firmware. Do I need to directly connect (e.g. via a coupler/barrel connector) each Orbi to make ethernet backhaul work?
Thanks!
Edit: tiny edit to better reflect network topo.
You might try changing the configuration to daisy chain the 2nd Satellite off the first one, instead of both connected to the same switch and see if this changes anything. Don't enable Daisy Chain on the router. Just see if adding the 2nd Sat to the back of the 1st Sat does anything different. I would also just as a quick test, take the switch out of the mix and directly connect both to the Orbi router. See if anything seen is different.
I have this similar network configuration. There is 2 unmanaged switched between my 1 satellite and the router. I don't have a 2nd Sat at this time so I can't test this with you.
Is this your switches?
http://us.dlink.com/products/business-solutions/dgs-1100-16/
If so, these are managed switches...
I'll give that a try -- although this is one of those things where (this time!) I didn't change anything. There was a change within Orbi that made bridging different. I just am not sure what changed.
And yes, those are managed switches -- but like I said the configs are both factory default with no changes.
Thanks for the help!
Something to narrow down, go direct with the Satellites to test with the router.
Even though using default settings, there maybe differences between these managed switches vs non manages switches that could be causing problems with newer FW. Seems to be a change in FW though.
Is the Orbi is running in router mode or AP mode?
Just connected one satellite directly to a 2nd LAN port on the router. By the time I got to the satellite it had a blue ring. Looked at router web UI and see that it still says it's backhauled to the router via 5G. Didn't reboot anything but ran a speed test via the now hard-wired sattelite and saw 700+mbits - Which means that the web UI must be out of date because I wouldn't see that speed from that satellite if it was backhaul'd via 5G. Going to do the same with the other wired satellite.
So this seems to indicate that something changed with the bridging where the satellites must be directly connected and not via the switch (since it will cause a storm). I do notice that spanning tree protocol is enabled on the router bridge (brctl show) but not on the satellite bridge. I'm not sure if that has something to do with it, but the fact that the firmware update introduced a loop into my network sure makes me think that's a good clue. Hope this helps.