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

Forum Discussion

bugs_galore's avatar
Sep 06, 2021

R7000 Wireless turning off then on at the wrong times

Having a problem with wirelss schedulling with R7000 using Advanced --> Advanced Setup--> Wireless Settings

 

I've set up start and end times, and have checked the "Turn off wireless signal by schedule" box.

 

Although the box does turn off then on at the correct times, with corresponding correct log entires, we're also seeing the wireless signal turn OFF then ON at many other times during the day, and this is shown in the log, although the OFF time is marked with an incorrect time whereas the ON time is marked with the correct time.  Note these incorrect OFF then ON events and log entries do not match the OFF/ON schedule showing in the wirelss settings gui.

 

This R7000 is running V1.0.11.126_10.2.112  firmware.

11 Replies

  • bugs_galore  I'm genuinely interested, is there some reason you want wireless scheduling? Personally, I just leave mine on all the time.

    • bugs_galore's avatar
      bugs_galore
      Guide

      Portwey84 - I want to turn it off at night after midnight so the kids don't stay up for hours on the internet.

       

      The feature is working at the intended time, but the side effects are that it's doing it randomly at many other times during the day.

      • bugs_galore's avatar
        bugs_galore
        Guide

        I have an update on this.  Was looking through all the logs (Administration --> Logs), and I see that every single time the wifi incorrectly turned OFF then ON, there was an NTP synch in between the incorrect OFF and the ON (putting it right) a minute later.

         

        And all the incorrect OFFs are tagged with the exact same incorrect time stamp: 3:29:39.  Which just happens to be during my gui-entered off time.

         

        My theory is the time in this R7000 can momentarily become incorrectly set to 3:29:29 during NTP sync.

         

        Note this deos not happen on every NTP sync.

         

        This looks like a bug in the R7000 to me.  Would be great if Netgear can comment if this is a known bug or if any fix will come.

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User

    Has a factory reset and setup from scratch been performed since last FW update?


    bugs_galore wrote:

    Having a problem with wirelss schedulling with R7000 using Advanced --> Advanced Setup--> Wireless Settings

     

    I've set up start and end times, and have checked the "Turn off wireless signal by schedule" box.

     

    Although the box does turn off then on at the correct times, with corresponding correct log entires, we're also seeing the wireless signal turn OFF then ON at many other times during the day, and this is shown in the log, although the OFF time is marked with an incorrect time whereas the ON time is marked with the correct time.  Note these incorrect OFF then ON events and log entries do not match the OFF/ON schedule showing in the wirelss settings gui.

     

    This R7000 is running V1.0.11.126_10.2.112  firmware.


     

    • bugs_galore's avatar
      bugs_galore
      Guide

      Hi FURRYe38 ,  I'm not sure if I ever updated the FW in this R700, although it does seem to be running what was the latest FW when I started this thread.  It would be very unfortunate if a factory reset were required after a FW update, rather than just a power cycle, but a quick google does show it's recommended.  Seems pretty drastic.

       

      I would have to learn how to save the config before doing a factory reset.

       

      Do you by any chance know if there's a way to check if a FW update was ever done?

      • FURRYe38's avatar
        FURRYe38
        Guru - Experienced User

        Well you reported in your first post:

        "This R7000 is running V1.0.11.126_10.2.112 firmware" 

        Which is one version behind: v1.0.11.128

         

        A reset is sometimes a valid step to help figure out issues and can lead to solved problems. Sometimes configurations can be hosed up after a FW update or configurations on prior versions are not fully compatible with new versions of FW. Maybe drastic but sometimes a necessary evil.