NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

RobOfTheNorth's avatar
Mar 11, 2021
Solved

RBS40 pulsing white after firmware update

This seems like a common problem, but nothing I've tired has solved it.... so posting here.

 

I noticed in the iOS Orbi app there was a firmware update available, so hit the update button. After the update was applied, my RBR40 and one RBS40 came up fine, but the 2nd RBS40 satellite never reconnected. The ring light is pulsing white, which indicates it's stuck applying the firmware update.

 

In the web console, the router shows up with 'backhaul status' good, as I'm using ethernet, but on the iOS app is shows magenta, and in the web firmware update page is says 'waiting for connection'. Also, no devices are connecting to it.

 

Here's what I've tried so far.

  • Press sync on router and then satellite
  • Turn off 20/40, dasiy chain, and other features.
  • Left it pulsing white overnight
  • Factory reset
  • Remove from orbi app and try to re-add satellite
  • Manually reapply the 2.6.2.104 firmware via tftp
  • Manually downgrade to previous 2.5.1.16 firmware via tftp

I'm out of ideas, and have exhausted all the suggestions I've seen online. The orbi continues to pulse white.

  • An update on this. I had left the RBS with the v2.5 firmware overnight and at some point it must have come out of its firmware update cycle. This morning it had reconnected and also, I assume, done an automatic update to v2.6.

     

    So, no real resolution other than to give the satellite days to finish it's update? Or perhaps it has some hidden long-cycle timeout recovery mode? It was strange that it reconnected since I had removed the satellite from my configurate and done at least 2 factory resets. So it shouldn't have had to appropriate key to resync.

     

    Any, issue resolved with no clue as to how.

1 Reply

  • An update on this. I had left the RBS with the v2.5 firmware overnight and at some point it must have come out of its firmware update cycle. This morning it had reconnected and also, I assume, done an automatic update to v2.6.

     

    So, no real resolution other than to give the satellite days to finish it's update? Or perhaps it has some hidden long-cycle timeout recovery mode? It was strange that it reconnected since I had removed the satellite from my configurate and done at least 2 factory resets. So it shouldn't have had to appropriate key to resync.

     

    Any, issue resolved with no clue as to how.