NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ORBI RBR50, RBS50 and other satellites (RBS20 & [RBR40 -> RBS40 hack])
So I have ORBI RBK50 (1xRBR50, 2xRBS50 ) [Orbi AC3000 ?] And recently one of my RBS50 is no longer functioning. I have my whole place wired cat6a, and use the ORBIs only for : phones, tablets/guest...
i finally got 2 of the older rbs20 satellites to work.
Sadly cant seem to get my other rbs50 working -- it powers up - the power led is green and the halo is flashing white.
Did numerous resets with paperclip - tried TFTP
PS S:\MY_DOWNLOADS\nmrpflash-0.9.18.2-win32> tftp -i 192.168.1.1 put RBS50-V2.7.4.24.img
Connect request failed
tried nmrpflash also to no avail
PS S:\MY_DOWNLOADS\nmrpflash-0.9.18.2-win32> .\nmrpflash.exe -L
PS S:\MY_DOWNLOADS\nmrpflash-0.9.18.2-win32> .\nmrpflash.exe -i net26 -f RBS50-V2.7.4.24.img
😞 might have to sell as parts .....is there a way to force the unit to upgrade itself using the USB2.0 slot on the RBS50 ?
My TV can update software using a USB stick, but (sadly) not any of the Orbi units. Netgear removed the USB port completely after the first models came out.
TFTP was quite an adventure for me. There is this distinct window of time during the startup when the unit looks for a TFTP connection. Too early: no good. Too late: no good. I was so frustrated after failing five times in a row that I was eyeing the trash can (either that or a hammer) and thought, "try one more time." The sixth time I hit it just right, and the firmware took.
TFTP is also sort of an ordeal because the computer running TFTP has to be connected only to the Orbi unit and has to have a static IP (because it cannot get an IP address from the network). All that cabling and re-cabling....
As I recall, when doing TFTP, the router is supposed to be at 192.168.1.1 and the satellites at 192.168.1.250. (But, it has been a couple of year and my memory never was all that great.)