NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 as AP with Ethernet Backhaul: Same switch for both WAN and LAN ports
I am thinking of the following configuration for wired Ethernet backhaul, but I am unsure if it will work. The RBR50 is already set to AP mode, and the satellites are in wireless backhaul current...
No, that configuration will not work and is not needed. When in AP mode the WAN port on the RBR acts like a LAN port and is on the LAN side of the network, no longer on the WAN side of the network when in router mode. LAN is bi-directional.
You can daisy chain switches and place them where needed to get a ethernet connection out to the farthest RBS. I have 4 switches in between my RBR and RBS currently using v2.5.1.8. Zero issues.
If you use managed switches, be sure that all IGMP protocols on these switches are disabled. Also disable any green ethernet features as well. These are known to cause problems in between RBR and RBS. Non managed, non green ethernet switches are preferred.
I wanted to add that this system currently has 4 RBS50 satellites, with Daisy Chain topology turned on.
The other item to note is that I have set the 5ghz backhaul channel to be fixed at Channel 108, based on the fact that there are several competing 5ghz signals at the 149 + range.
I MIGHT be able to switch off Daisy Chain and go to Star, because if I can get this one remote satellite to work via Ethernet backhaul, the other 3 satellites may be close enough to communicate with the Router via the 5ghz channel.
Would switching to Star help the config in any way? With 4 satellites, I see constant re-mapping occurring between the Router and the Satellites.
Thanks.
For ethernet backhaul, Daisy Chain really should be disabled. Thats meant for wireless connected RBS to piggy back of one another out in a line from the RBR. Hiaving DC on may see odd behaviors...You might try turning OFF all RBS accept for 1 then connect it up, then start adding RBS 1 at a time to see how it all behaves.
Yep. DC can definitely cause issues. The only reason that I have it on is for that one satellite in question. It is about 80' from the next closest satellite, and over 100' from the router - i had wanted it to connect via DC to the closer satellite, but it was only pullng the 2.4ghz backhaul, which was too slow for my client. So, it sounds like using the switches for E-backhaul and switching to Star topology will be a better option.
Tomorrow is the day we find out -- thanks for the input!
:smileywink:
starrs-ridge wrote:Tomorrow is the day we find out -- thanks for the input!:smileyhappy: