New - RBR50 / RBS50 Firmware Version 2.7.4.24 Released

---

pgrunwald wrote:

My RBR50 is at v2.7.3.22, showing 'no new firmware version available'

My RBS50 is at v2.7.3.22, showing 'no new firmware version available'

---

Netgear's firmware update process remains confusing.  There seem to be three independent processes going on:

• Netgear publishes new firmware on the support web site.  For the RBR50 product, this is at:
  https://www.netgear.com/support/product/RBR50.aspx#download 
  This web page shows that V2.7.4.24 is now available.  If customers discover this new version, read the release notes,
  and decide to install it on their system, then can download the *.zip files, extract the firmware images, and use the
  Manual Update feature to load it on their router and satellites.
• At some point, Netgear activates the Automatic Update feature which allows the router to "find" this new firmware and offer to load it.  Customers who never look at the firmware update feature will be blissfully unaware of it.  This process appears to be "rolled out".  My RBR50, for example, continues to report "No new firmware available."
  For those who do discover the new firmware, installing it remains optional.
• At some point, Netgear has the option to install the new firmware automatically, usually in the middle of the night.  Customers who look at the management interface (or the app) may realize, "hey. the firmware updated by itself."  Customers who never look at the management interface will remain blissfully unaware that this has happened.  This process appears to be "rolled out" over a period of time.

When the Orbi system is behaving strangely, one step that is often recommended is to update the firmware to the latest release.  This may be not so much in hopes that it will fix the problem as in the realization that the first thing others will recommend is to update the firmware. Might as well get that out of the way.

In the case of these incorrect IP addresses, I have low expectations that newer firmware will remedy the problem.

Diagnosing this sort of thing is rather technical.  My tactic would be to activate the debug option to "Capture LAN\WAN traffic", restart the problem device, save the debug zip file, and then open the file lan.pcap with Wireshark and look for the DHCP assignment to see where it came from.