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

Forum Discussion

bdgregg's avatar
bdgregg
Aspirant
Sep 29, 2018
Solved

Netgear Nighthawk R8300

I recieved an email today that there is a new firmware update for my router due to security reasons, the email references V1.0.2.122

I see on the support web site that there is indeed a new version of the firmware available - V1.0.2.128 - https://kb.netgear.com/000060248/R8300-Firmware-Version-1-0-2-128  Note that the web site lists a newer version than the email referenced.

When I go into my router and have it check for an update, it reports that there are no updates available and it is at version V1.0.2.122.

 

Which is correct? The KB or my router?  Why doesn't the router know that there is a new firmware file to download?  I'm afraid that if I download the firmware from the web site and upload it to the router that it will brick the router.  I've decided to hold off until I feel more comfortable about this.

 

Any help would be appreciated to clear up the matter.

Thanks,

Brian.

 

  • HI Bran,

    Always use the Support Portal for the latest and most up FW version available for your product.

     

    https://www.netgear.com/support/product/R8300#download

     

    Updating should be performed manually.  Sugget you not use an App or the Auto Check and Update feature in the Routers GUI.  Updates should be planned.  Do them manually yourself, and on your terms.

2 Replies

  • HI Bran,

    Always use the Support Portal for the latest and most up FW version available for your product.

     

    https://www.netgear.com/support/product/R8300#download

     

    Updating should be performed manually.  Sugget you not use an App or the Auto Check and Update feature in the Routers GUI.  Updates should be planned.  Do them manually yourself, and on your terms.

    • bdgregg's avatar
      bdgregg
      Aspirant

      I updated the router to the newer version found on the support site and it worked properly.

       

      Thanks,

      Brian.