NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 Continually Reboots after Firmware Upgrade V7.2.6.21_5.0.20
I have an RBR850 with two satellites. The two satellites are using wired backhaul here is the setup ISP-->Router/FW (DHCP)-->Managed Switch-->RBR850, RBS850 and RBS850 all on separate ports on...
The Internet port is required in router or AP mode for the RBR to work correctly.
What brand and model is this switch?
Be sure that the RBS are ethernet connected to the back for the RBR or with the switch connected to the back of the RBR then RBS connected to the switch in this configuration:
You can't (without issues) do it the way you have it set.
It should go modem/gateway--->RBR (into its wan port---->switch/satellites.
If you're going to put the switch before the RBR, then the satellites need to direct connect to the RBR's lan ports. Or a 2nd switch used connected after the RBR for the satellites to connect it (if you're needing more ports)
One situation that has come up on the forum is adapting network gear to existing in-house wiring. It is now common to find a house "pre-wired" with Ethernet jacks located in many rooms of the house, each with a single Ethernet cable running to a patch panel in some location. Often this location was chosen because at the time it seemed a good compromise between cost, ease of installation, and other factors. The installation often included coaxial cable to bring the Internet Service Provider signal to the patch panel. (Optical fiber is a relatively recent development. Often WiFi was limited to 2.4G which has greater coverage area than more modern 5G - and now 6G.)
From posts on the forum, it has become clear that some users do not find the patch panel location suitable for their WiFi router. They want to place the WiFi router somewhere else and also locate satellite units in other locations. Alas, there is only one Ethernet cable from the patch panel to each location. While it may have been routine to install cable when the walls were open, retrofitting more cables can be a nightmare (expensive, disruptive, etc.)
This can lead to situations like this discussion. Place the ISS router and a switch at the patch panel and connect everything in the house to the switch. Netgear's Orbi product, however, is not designed for this. (Maybe other products are?)
There was a discussion on the forum about how to use one Ethernet cable to carry:
- The ISP connection from the patch panel to the router WAN port, and
- The router connection from LAN ports to satellites
The concept is illustrated with this diagram:
The managed switch at the patch panel has two port based VLANs:
- VLAN1 connects the ISP router and any miscellaneous devices around the house.
- VLAN2 connects the Orbi satellites to the swith
There is one "Tagged" VLAN port, which carries VLAN1 and VLAN2.
At the WiFi router location, there is a second managed switch with two port based VLANs:
- VLAN1 carries traffic to the router WAN port
- VLAN2 carries LAN traffic destined for Orbi satellites
There is one "Tagged" VLAN port, which carries VLAN1 and VLAN2 traffic. In addition, if the user desires, miscellaneous devices can be connected to this second switch as Port Based VLAN (1 or 2. Doesn't really matter.)
The "magic" comes from VLAN tagging. Once the Ethernet switches have used ARP to discover where everything is, they know which port to use to reach every device. None of the devices themselves are aware of the VLANs. If a packet comes into the switch on a VLAN1 port, it can only go to other VLAN1 ports. (Same for VLAN2) So, packets from the ISP router will never go directly to Orbi satellites, because they are on VLAN2.
I think this is close to my solution minus the VLAN tagging which I can implement. Apologies for the rudimentary diagram but here is the current network topology.
I do not understand why I should/would put an ORBI in front of either the first managed switch in the basement or worse yet the first device after the ISP.
With ARP and IP addressing I'm unclear why RBS 1 and 2 can't reliably find RBR.
As of now all three APs are working and passing wireless traffic but RBR can't "see" the RBSs in the App or Web GUI.I can VLAN them but it too seems odd to me.
You'll notice the purple dotted line was one answer given. When that happens the RTR goes pink and all traffic is lost on that AP. Feel like that is creating a network loop and bringing a halt to traffic.
CrimpOn wrote:
Operating a very similar config for the normal standard router configuration and testing.
Connecting an MR60 with the WAN on a DMZ VLAN and IP subnet, plus the LAN on a dedicated VLAN and subnet (with IPv6 operational in Auto mode) to connect one or two MS60 on an access port for the LAN VLAN - and all hell does break loose on my all of my networks. 8-/
I guess I could relocate the RBR to the basement (hurting wireless coverage) but if it is in AP mode and just relaying traffic what is the technical reason it has to be in front of an actual managed switch. Unless there is just some limitation in the Orbi to find other devices on the network.
Manages switch are known to cause problems for Orbi systems and the connecting RBS. Router or AP modes. Especially for ethernet connected RBS. Some users have been able to make them work with managed switches by disabling all IGMP Protocols and Green Ethernet features on thise switches. However when those don't work, un-managed switches are recommended in between the RBR and RBS for best connection and operation for ethernet connected RBS.
This is the commended configuration for ethernet connected RBS if you have a LAN swtich in the mix:
NG GS-105/108v4 and GS308v3, D-Link DGS-105/108 and HP ProCurve 1400 series non managed switches work for Orbi systems.
vader716 wrote:
I guess I could relocate the RBR to the basement (hurting wireless coverage) but if it is in AP mode and just relaying traffic what is the technical reason it has to be in front of an actual managed switch. Unless there is just some limitation in the Orbi to find other devices on the network.
