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

Forum Discussion

gr8sho's avatar
gr8sho
Virtuoso
Dec 13, 2019

Firmware v2.5.1

New version available. Based on the description, doesn’t seem worth the disruption.

New Version: V2.5.1.8

Release Notes:
[Bug Fix] Fixes JP/AU/CA region can't firmware update issue. [Bug Fix] Fixes Armor activation failed due to device offline issue.

100 Replies

  • I shall wait until it's officially posted on the Supprt pages and then take a view.

    • gr8sho's avatar
      gr8sho
      Virtuoso
      Can’t edit original post to point out the update is offered through the iOS app.
      • MikeG63's avatar
        MikeG63
        Apprentice

        Actually if you log in into the web based admin page for the router and satellites it also shows as an available firmware update.

  • No meantion of device naming problem. Hmmm. :smileyfrustrated:


    gr8sho wrote:
    New version available. Based on the description, doesn’t seem worth the disruption.

    New Version: V2.5.1.8

    Release Notes:
    [Bug Fix] Fixes JP/AU/CA region can't firmware update issue. [Bug Fix] Fixes Armor activation failed due to device offline issue.

     

  • The first issue I'm experiencing with firmware 2.5.1.8 is the inability to turn on remote management from the app. I can enable it from the web interface but the app does not allow me to enable it so I can access my Orbi remotely from the app. I did a full restore back to factory settings before applying the update.

     

    I receive the following error:

    "Some error occured while enabling/disabling remote management"

    • CrimpOn's avatar
      CrimpOn
      Guru

      My community forum page has an orange banner across about "an issue with Remote Management fucntionality."  (That won't go away when I click on the 'x', but that's another issue.)  They say it's fixed, unless it's not fixed.

    • tomschmidt's avatar
      tomschmidt
      Virtuoso

      For those that have installed v2.5.1.8 firmware, have you checked to see if the https certificate is updated to be properly signed by a certificate authority?  Does opening https://orbilogin.net/ open as a secure web site in your web browser?  Can you check the certificate for when it will expire again?

      • gr8sho's avatar
        gr8sho
        Virtuoso

        tomschmidt wrote:

        For those that have installed v2.5.1.8 firmware, have you checked to see if the https certificate is updated to be properly signed by a certificate authority?  Does opening https://orbilogin.net/ open as a secure web site in your web browser?  Can you check the certificate for when it will expire again?


        Chrome complained, so it still appears broken to me.

    • FURRYe38's avatar
      FURRYe38
      Guru

      I would post about this in the Orbi app forum:

      https://community.netgear.com/t5/Orbi-App/bd-p/en-home-orbi-app

       

      Ensure the Orbi app is up to date as well. 


      rhino-1 wrote:

      The first issue I'm experiencing with firmware 2.5.1.8 is the inability to turn on remote management from the app. I can enable it from the web interface but the app does not allow me to enable it so I can access my Orbi remotely from the app. I did a full restore back to factory settings before applying the update.

       

      I receive the following error:

      "Some error occured while enabling/disabling remote management"


       

      • DWHITE4245's avatar
        DWHITE4245
        Aspirant

        2.5.1.8 no longer seems to be available from the Downloads area. I get 'File not found'.

    • SW_'s avatar
      SW_
      Prodigy

      Interesting observation from Voxel:

       

      Voxel wrote:

       

      2.5.1.8 was released after I prepared my version... I do process this version (GPL sources) since yesterday (2.5.1.8) and I've seen the changes in device name processing (net-scan package is disabled and attached-devices package is used now)...

       

       

      • Wonder what the differences is. 


        SW_ wrote:

        Interesting observation from Voxel:

         

        Voxel wrote:

         

        2.5.1.8 was released after I prepared my version... I do process this version (GPL sources) since yesterday (2.5.1.8) and I've seen the changes in device name processing (net-scan package is disabled and attached-devices package is used now)...

         

         


         

  • At somepoint NG may put up FW version up on there update servers that users can press the check for update button to see if something is there and the Orbi may find something. It's up to NG to post FW updates on there servers, or not. 

     

    When it's not detected then it's up to users to manually update FW if they choose too. NG seems to be more flexible in this regard. It was just a couple of years ago that NG was pushing each and every FW update which for some users, broke the Orbi operation, thus making users angry. So with all the feedback, NG has relented now and give users more control over FW updates. So lets not look a gift horse in the mouth. Users can update manually, or not. Theres an old saying, "If its not broke, don't fix it!!!" 

  • Before I updated to V2.5.1.8 I could see all of my 84 attached wi-fi devices. Since the update, I never see more than 4 attached devices. I have rebooted the router and the three satellites 3 times. Nothing changes! HELP! What happened?
    • FURRYe38's avatar
      FURRYe38
      Guru

      Clear all browser caches, exit the browser then relauch and open the page. 

      Does a different browser exhibit the same thing?

       

      Try a factory reset on the RBR and setup from scratch. 


      isareeves wrote:
      Before I updated to V2.5.1.8 I could see all of my 84 attached wi-fi devices. Since the update, I never see more than 4 attached devices. I have rebooted the router and the three satellites 3 times. Nothing changes! HELP! What happened?

       

      • isareeves's avatar
        isareeves
        Tutor
        Thank you... I tried all of your suggestions. Still no luck. ☹️
    • tomschmidt's avatar
      tomschmidt
      Virtuoso

      isareeves, are you using the iOS app, Android app, or web interface to see the attached devices?  There have been some users reporting that the iOS app has issues properly displaying the devices under the v2.5.1.8 firmware, but the web interface and Android app show them properly.  If you are using the iOS app, then check your device list using the web interface.  If that is your issue as well, there is a thread on the iOS issue under the Application forum. See https://community.netgear.com/t5/Orbi-App/Orbi-iOS-App-not-working-after-router-upgrade-to-2-5-1-8/m-p/1853404

       


      isareeves wrote:
      Before I updated to V2.5.1.8 I could see all of my 84 attached wi-fi devices. Since the update, I never see more than 4 attached devices. I have rebooted the router and the three satellites 3 times. Nothing changes! HELP! What happened?

       

      • isareeves's avatar
        isareeves
        Tutor
        Thank you... I use my Orbi with IOS 13.3.1... my devices still do not show up correctly after clearing my cache, reinstalling the app (which I found out was a huge mistake), nor on Chrome or Safari (after clearing the cache). I was about to wipe everything out and start clean until I read that it most likely not make a difference, since I would be restarting on the same version of the firmware. I am too frustrated to try anything else. I guess I will wait for a new firmware update.
  • Ever since upgrading (automatically) to v2.5.1.8 everything on the network has been dropping connection. I mean everything because it's roku's, PC's (windows), phones (android), xbox connected to the satellite. It' fairly often (maybe every 15 minutes) and lasts for maybe 5-15 seconds. Never had any problems before.  

     

    I was going to roll back to v2.3.5.30 but when I go to the manual update page it only gives me the option to "check" one satellite so it worries me to try and roll back. 

    Two questions.

    1. Is anyone else having problems with v2.5.1.8

    2. Why would only one satellite be showing up on the manual upgrade page. 

    • gr8sho's avatar
      gr8sho
      Virtuoso
      2.5 has been out for months.
      For expediency, consider a factory reset.
    • FURRYe38's avatar
      FURRYe38
      Guru

      No issues since v2.5.1.8 loaded on my RBK50. No DNS timeouts, blocked web sites, wifi or internet drops. Device naming is fixed on this version. Though on RBS in a web browser, it shows "unknown" for device names. Most stable version to date. 

       

      Factory reset is recommended then setup from scratch. I reset mine after each update and save a new backup configuration to file for safe keeping. 

       

      What is the Mfr and model# of the ISP modem the NG router is connected too?

      What is the size of your home? Sq Ft?
      What is the distance between the router and satellite(s)? 30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected. https://kb.netgear.com/000036466/How-far-should-I-place-my-Orbi-satellite-from-my-Orbi-router

       


      bolingde wrote:

      Ever since upgrading (automatically) to v2.5.1.8 everything on the network has been dropping connection. I mean everything because it's roku's, PC's (windows), phones (android), xbox connected to the satellite. It' fairly often (maybe every 15 minutes) and lasts for maybe 5-15 seconds. Never had any problems before.  

       

      I was going to roll back to v2.3.5.30 but when I go to the manual update page it only gives me the option to "check" one satellite so it worries me to try and roll back. 

      Two questions.

      1. Is anyone else having problems with v2.5.1.8

      2. Why would only one satellite be showing up on the manual upgrade page. 


       

      • bolingde's avatar
        bolingde
        Guide
        Thanks for suggesting factory reset,, but I'll think I'll hold off that mess for awhile.
        None of the other really matter because it was all working before v2.5.1.8