NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi 960 Wired Backhaul Requirements
Good morning, does anyone know if there are any specific requirements for wired backhaul on these units? On my previous XS508M switches they would connect wired without any issues. Since changing t...
jabenedicic wrote:
Device name is greyed out and not available in AP mode.
Well, that's annoying! Sheesh. What about changing the mode to router temporarily, set the name, then switch back to AP mode?
It wipes the config changing modes.
Well, that was fun!
I have a spare RBR750 router that can be connected to the network for testing.
- In router mode, I set the Device Name: "Test750"
- In the Internet table, set it to use 1.1.1.1 and 8.8.8.8 for DNS.
- Because it is connected to an existing system, the Orbi automatically changed the LAN subnet to 10.0.0.0.
- In the LAN setup table, defined a laptop and tablet with reserved IP addresses
- 10.0.0.2
- 10.0.0.3
- Verified with the Orbi app that the Network Map showed the router as "Test750"
- Changed from Router Mode to Access Point Mode.
- (after waiting... and waiting...)
- The 750 appeared in the primary system with the name "Test750"
- Verified with the Orbi app that the Network Map still shows the router as "Test750"
- Logged into the 750 web admin and now it shows all sorts of devices connected (from the primary system)
- Changed the 750 back to Router Mode.
- (waited... waited...)
- Now, it is back to being 10.0.0.1 in Router Mode.
- Logged into the web interface.
- Device Name remains "Test750"
- DNS entries remain 1.1.1.1 and 8.8.8.8
- Two assigned IP addresses remain 10.0.0.2 and 10.0.0.3
Thus, my conclusion is that changing from router to AP mode (and back) does not "wipe" the configuration.
Plus, why would I care? In AP mode, there is nothing to configure except the WiFi SSID/password.
- I’ll give that another go when I can swap things around again. When I initially swapped it over I had nothing carry over, but that might be my fault. I had some weird issues when I first moved it over as I hadn’t changed the LAN cable over from the 2.5GbE port to the 10GbE WAN port.
In other news, I finally found where they hide the IGMP Snooping feature in Netgear Insight, disabled that on the VLAN, but still no luck on the backhaul working. The AP gets an IP address and I can get to the web interface, it just never shows up in the list of satellites or seems to work at all.
Although I’ve found a shed load of other issues in the Insight Managed mode of the switches, things that used to work when I had them locally managed, like LACP to my NAS, just no longer works. I’m going to end up changing these back to locally managed mode and see if I can find any more settings that I can disabled to get the wired backhaul working.
While the Insight management is a nice idea and having an app/cloud based management is convenient. The fact is doesn’t have feature parity with the local interfaces and the design of the system feels like Netgear don’t hire UX people at all, just makes it unusable.I recommend in short term, you find a non managed 1Gb switch or try GS110MX for 2.5Gb support and see if you can get the RBS ethernet connected properly. The RBS can be 1Gb or 2.5Gb connected.
Seems like this MS model switches maybe causing problems here.
