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...
FURRYe38
Apr 02, 2018Guru - Experienced User
OK, just asking. Was a full factory reset performed on both router and Satellites and setup from scratch yet?
Any network switches between the router and satellite?
What is the mfr and model# of the ISP modem your using?
When trying to use Daisy Chain, I presume you physically have the Satellites piggy backing of each other and not wired for back haul ?
I would also try this. Test with the router alone. Turn off all Satellites. Then graduate by adding one Satellite via wireless. Test for issues. Then add another.
packetwerks
Apr 02, 2018Star
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.