NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBS50v2 power led flashing red
Hi there,
seems there is a problem with the firmware update to 2.7.4.24. I have 1 Router RBK50 and 2 Statellites RBS50. Router and 1 Satellite have been updated correctly, even I was not really aware of the update. I accidentally found out that 1 satellite was not connected anymore.
Orbi App says that the firmware is 2.7.3.22 on the satellite, the satellite is not connected, the white led is flashing and the power led is flashing red. So, I googled and found out that the problem is widely known, but I did not find a solution for that. Manual update does not work, because satellite is not connected respectively can not added to the system. Reset button does not help either.
How to get the latest firmware on the satellite or to bring the satellite to a status which allows the router or the Orbi app to identify the satellite? Any advice welcome.
Thanks
PROBLEM SOVELD!
I did it along the very good description from shrickus posted 2018-08-13 09:56 PM, but I did it in a Mac environment.
Some observations: mini hub is essential to see that Mac AND satellite are connected. tftp works slightly different - you need three steps:
tftp 192.168.1.1
binary
put <firmware version img file>.
Worked out for me with an RBS50v2 satellite and fw version 2.7.4.24 and gives me trust for the next fw update.
Thanks shrickus
Tilo
6 Replies
Replies have been turned off for this discussion
tiweme how did you do it in mac? All the explanations, including in videos on Youtube, are on how to fix this on Windows and I am just getting desperate. Have done everything I can, nothing works.
Hi clarasousa ,
here comes the original post from shrickus :
--------------------------2018-08-13 12:56 PMSOLVED! Thanks for the hints, everybody... here is what I ended up doing:
You were correct that the satellite IP address was indeed 192.168.1.1 -- but I was not able to either ping that address or see it with the port scanner (since no ports were active, I guess?)
I manually set the PC's lan port to 192.168.1.68, and plugged it directly into the WAN port of the RBS40 (port #1) using a standard ethernet cable. This caused my PC to disable the ethernet port, so I plugged the PC into a mini-hub first. Once the network activity light showed that the PC was active, I plugged the satellite lan port #2 into the hub. While holding the reset button in, I powered up the satellite and continued to hold the reset button until the power led started flashing red (10-15 sec). At that point it was connected to the network using the default id address.
Based on other tips, I activated the TFTP feature on the PC, started a Powershell as Administrator, and successfully pushed the latest firmware image onto the satellite, using:
`tftp -i 192.168.1.1 PUT .\RBS40-V2.1.4.16.img`
I could watch the lights on the hub flashing as the file was transferred, and when they stopped I could see in Powershell that the transfer was successful. After a power cycle, the satellite booted up as expected, and I could sync it with the router. Sweet!
-----------------------This worked very well with my slight modifications regarding tftp usage. Important: Please use a mini-hub for connecting the satellite and the Mac. It does not work if you connect satellite and Mac directly with an ethernet cable.Good luck,Tilo- Thanks so much guys. It is working again following your indications!
Might try with this in Mac:
PROBLEM SOVELD!
I did it along the very good description from shrickus posted 2018-08-13 09:56 PM, but I did it in a Mac environment.
Some observations: mini hub is essential to see that Mac AND satellite are connected. tftp works slightly different - you need three steps:
tftp 192.168.1.1
binary
put <firmware version img file>.
Worked out for me with an RBS50v2 satellite and fw version 2.7.4.24 and gives me trust for the next fw update.
Thanks shrickus
Tilo
If you got the RBS working again. Then you could manually update the RBS then RBR to most current version of FW using the WEB UI on the RBS and RBR:
