NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Added RBS50 is Sync'd, Had IP address but IP/Bakhaul doesn't show in GNU
I purchased a used Orbi RBS50 to add a 3rd to my existing system that includes the RBR50 and two RBS50 units supplied with the original system. The 3rd RBS50 easily sync'd and showed in GNU as 3rd s...
GNU is what I thought this forum has been refering to the RBR50 Orbilogin.net application, it says that at teh bottom. The 3rd device does go thorugh the start up and flashes blue at the end but isn't connecting any devices nor is it doing more than a switch with regards to passing through wired internet; must be wired to router to allow wired device to get connected.
The lack of an assigned IP address in the RBR50 Obilogin.net is different than when first connected with a different, earlier firmware version in the 3rd RBS50. After firmware upgrade to match rest of my Orbi system, the IP address that was visible is now gone. Never got it communicating with different firmeware versions so I am thinking that going back to original is wrong direction.
GMHunter wrote:GNU is what I thought this forum has been refering to the RBR50 Orbilogin.net application, it says that at teh bottom. The 3rd device does go thorugh the start up and flashes blue at the end but isn't connecting any devices nor is it doing more than a switch with regards to passing through wired internet; must be wired to router to allow wired device to get connected.
The lack of an assigned IP address in the RBR50 Obilogin.net is different than when first connected with a different, earlier firmware version in the 3rd RBS50. After firmware upgrade to match rest of my Orbi system, the IP address that was visible is now gone. Never got it communicating with different firmeware versions so I am thinking that going back to original is wrong direction.
Thanks for the explanation about "GNU". Actually, Netgear is explaining that the Orbi software is issued under the GNU license because it is based on OpenWRT, which is open source software. It has a nice ring to it. I usually describe "Orbi web interface" vs. Orbi "app" (which is nearly worthless in my opinion).
My usual tactic is to do bring the satellite into the same room with the router (which avoids running back and forth), no ethernet cable for now, perform a "Factory Reset" on the satellite https://www.youtube.com/watch?v=cMw4ePACgc4 , then open the Orbi web interface and select "Add Orbi Satellite" (bottom menu item). Until the satellite properly syncs with the router over WiFi, there is little point to attempting ethernet connection. Once the WiFi backhaul is working correctly (satellite appears on Attached Devices), then an ethernet patch cable can be plugged in.
Attached Devices does not update instantly I switched a laptop from ethernet to WiFi and it still showed up as connected for several minutes even though the cable was clearly unplugged. The process of checking connections and updating Attached Devices appears to have several "timers" running. Just in general, I find that computers are not very "fast" about doing things like starting up, updating, etc.
It is generally felt that the best practice is to have all Orbi units on the same firmware.
If you can give it another try, please describe what happens this time.