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

Forum Discussion

sir_bazz's avatar
sir_bazz
Apprentice
Apr 11, 2016
Solved

R7000 Beta FW 1.0.5.60

Downgrading from Beta 1.0.6.40 to 1.0.5.60, (with Arlo disabled), creates a new nameless SSID.   Mac begins with C6:04:15   Obviously no Arlo settings in 1.0.5.60 so no way disable it   Disabli...
Firmware
  • Retired_Member's avatar
    Retired_Member
    Apr 11, 2016

    Did you factory reset after the FW changes. If you didn't the arlo SSID named or non broadcasted SSID could still be present.

     

    After testing and reverting to 4.30 arlo ssid was present when I disabled both 2.4 & 5g until I factory reset a 2nd time.

Retired_Member's avatar
Retired_Member
Apr 11, 2016

Did you factory reset after the FW changes. If you didn't the arlo SSID named or non broadcasted SSID could still be present.

 

After testing and reverting to 4.30 arlo ssid was present when I disabled both 2.4 & 5g until I factory reset a 2nd time.

sir_bazz's avatar
sir_bazz
Apprentice
Apr 11, 2016

Thanks for the reply searay.

 

Didn't bother with the reset as it's easier to rollback the firmware than re-enter all the settings again.

 

I don't think a firmware change should require a factory reset, (or even two as in your case), to remove unintended behaviours.

 

Was posting as a bug report in the firmware but will flag your reply as the solution for anyone who faces the same issue and wants to resolve it.

  • netwrks's avatar
    netwrks
    Master
    Apr 11, 2016
    sir_bazz wrote:

    Thanks for the reply searay.

     

    Didn't bother with the reset as it's easier to rollback the firmware than re-enter all the settings again.

     

    I don't think a firmware change should require a factory reset, (or even two as in your case), to remove unintended behaviours.

     

    Was posting as a bug report in the firmware but will flag your reply as the solution for anyone who faces the same issue and wants to resolve it.

    Actually,  a very high percentage of router issues identified on this forum, is a direct result of NOT resetting to factory default, after a firmware upgrade. We just don't say it because we don't know what else to tell you. The reason being, it is the only way new drivers etc (or any other additions / deletions) will correctly load, or be deleted. It  also removes any firmware and configuration artifacts (stuff that lingers form old to new firmware versions) that can (and really do) cause grief after firmware upgrades. Especially true if you have never reset a router to factory default. Oh, and don't load configs from previous versions of firmware. That's just shooting yourself in the foot.. At least at the end, you are starting with a clean slate on the router.  A few minutes of pain, vs. alot of gain..

    • sir_bazz's avatar
      sir_bazz
      Apprentice
      Apr 11, 2016

      Yes of course.  No denying it's the big hammer fix for when things don't go quite right with the upgrade process.

      Infact IIRC, clearing NVRAM used to be included in the release notes as part of the upgrade process for older firmwares, (for the R7000 anyway).

       

      I recently upgraded from the very old firmware R7000-V1.0.3.61_20140605_QA to 1.0.6.40 and everything just worked without having to clear NVRAM or manually re-enter settings.  And that must've involved alot more changes to drivers, settings, secrity fixes, new features, etc than the average upgrader would experience, (R7000 comes default with 1.0.4 now).

       

      On the other hand, I've also installed newer firmwares, (including the supposed stable releases), performed the resets, reconfigured settings from scratch, and still experienced issues at the other end.

      The easy fix for me has always been to go back to R7000-V1.0.3.61_20140605_QA and is the reason I've continued to use it for nearly two years now.

       

      Still it's good that access to the big stick, ie. the factory reset, is still available as it does fix alot of config issues that stem from upgrading firmware on this device.