NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ethernet backhaul for CBR40
The website discusses how to set up ethernet backhaul for the Orbi system but the list of covered models does not appear to include the Orbi cable modem CBR40. I have a new place under construction ...
You can connect the CBK40 with RBS series satellites. The one that comes with the CBK40 is a RBS20.
What is the Mfr and model # of this switch?
I have mine connected thru two 1G NON Managed switches. Managed switch seem to give problems with Orib systems. If you have a managed switch, first try connecting the satellite directly to the Orbi router and by pass the managed switch if you seem to experience problems with wired back haul.
For Managed switches, one user meantioned that he disabled IGMP protocols on the his switch and it resolved the wired back haul problems he was seeing.
thanks
The 10G switch I want to use in an Orbi mesh system is Netgear XS724EM-100NAS 24-port 10-Gigabit / Multi-Gigabit Ethernet Smart Managed Plus Switch | 2 x 10G SFP+ Fiber ports | Rackmount | 24 x Multi-speed ports | ProSAFE . But because the system will involve two outbuildings, I want to use Cat6A ethernet backhaul, which is why I wondered if that were possible with the CBR40.
Cat6A cabing is mainly for inwall and runs. I have in wall CAT6A in my home. Before and after is all CAT6 patch cabling. I have a non managed switch after the CBR40. Then other non managed switches at remote locations. This has been working since day one when I got the CBK40.
The switch your suggesting is a managed switch. I would make sure that you can disable IGMP protocols on this switch or you may have problems with the Orbi system.
I would first contact someone higher level, L2 or L3 in NG support and ask about compatibility with this switch and the Orbi system. Been a few users post about managed switches in the main ORBI forum and having bad experiences with managed switches. Not sure if this was ever addressed by NG. The only user posted that he found that disabling IGMP protcols on his switch seemed to fix his experiences: