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

Forum Discussion

IrvSp's avatar
IrvSp
Master
Jun 24, 2016
Solved

R7000, F/W V1.0.5.70, Time Sync approximately every 1 and 1/2 hour.

I reported this to ElaineM a few weeks ago with no answer other than she'll contact support. This started a few weeks ago. This is a snippet of my log with no deletions:

 

[Time synchronized with NTP server] Friday, Jun 24,2016 06:42:23
[Internet connected] IP address: 184.88.9.110, Friday, Jun 24,2016 06:42:23
[DHCP IP: (192.168.1.12)] to MAC address 84:89:AD:71:97:B2, Friday, Jun 24,2016 06:28:26
[Time synchronized with NTP server] Friday, Jun 24,2016 05:16:03
[Internet connected] IP address: 184.88.9.110, Friday, Jun 24,2016 05:16:02
[Time synchronized with NTP server] Friday, Jun 24,2016 03:49:43
[Internet connected] IP address: 184.88.9.110, Friday, Jun 24,2016 03:49:42
[Time synchronized with NTP server] Friday, Jun 24,2016 02:23:23
[Internet connected] IP address: 184.88.9.110, Friday, Jun 24,2016 02:23:23
[DHCP IP: (192.168.1.3)] to MAC address A4:67:06:57:DD:0E, Friday, Jun 24,2016 01:03:55
[Time synchronized with NTP server] Friday, Jun 24,2016 00:57:02
[Internet connected] IP address: 184.88.9.110, Friday, Jun 24,2016 00:57:02
[DHCP IP: (192.168.1.11)] to MAC address 98:01:A7:05:5D:8C, Friday, Jun 24,2016 00:43:07
[Time synchronized with NTP server] Thursday, Jun 23,2016 23:30:42
[Internet connected] IP address: 184.88.9.110, Thursday, Jun 23,2016 23:30:42
[Time synchronized with NTP server] Thursday, Jun 23,2016 22:04:23
[Internet connected] IP address: 184.88.9.110, Thursday, Jun 23,2016 22:04:22
[Time synchronized with NTP server] Thursday, Jun 23,2016 20:38:01
[Internet connected] IP address: 184.88.9.110, Thursday, Jun 23,2016 20:38:01
[DHCP IP: (192.168.1.5)] to MAC address 10:AE:60:57:25:06, Thursday, Jun 23,2016 19:27:02
[DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:5B, Thursday, Jun 23,2016 19:14:04
[Time synchronized with NTP server] Thursday, Jun 23,2016 19:11:45
[Internet connected] IP address: 184.88.9.110, Thursday, Jun 23,2016 19:11:45
[DHCP IP: (192.168.1.12)] to MAC address 84:89:AD:71:97:B2, Thursday, Jun 23,2016 18:21:33
[Time synchronized with NTP server] Thursday, Jun 23,2016 17:45:21
[Internet connected] IP address: 184.88.9.110, Thursday, Jun 23,2016 17:45:20

Prior to this happening it happened no more than twice a day. Also occasionally I see a DISCONNECT before the sync...

 

[Admin login] from source 192.168.1.30, Sunday, Apr 17,2016 08:30:18
[Time synchronized with NTP server] Sunday, Apr 17,2016 08:08:13
[Internet connected] IP address: 184.88.9.110, Sunday, Apr 17,2016 08:08:12
[DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:5B, Sunday, Apr 17,2016 06:26:31
[DHCP IP: (192.168.1.2)] to MAC address A4:67:06:57:DD:0E, Sunday, Apr 17,2016 02:01:35
[DHCP IP: (192.168.1.3)] to MAC address 1C:AB:A7:F0:61:EB, Sunday, Apr 17,2016 01:50:50
[DHCP IP: (192.168.1.4)] to MAC address 10:AE:60:57:25:06, Sunday, Apr 17,2016 01:27:09
[DHCP IP: (192.168.1.4)] to MAC address 10:AE:60:57:25:06, Saturday, Apr 16,2016 13:55:56
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Apr 16,2016 13:51:08
[DHCP IP: (192.168.1.3)] to MAC address 1C:AB:A7:F0:61:EB, Saturday, Apr 16,2016 13:51:04
[Time synchronized with NTP server] Saturday, Apr 16,2016 13:51:04
[Internet connected] IP address: 184.88.9.110, Saturday, Apr 16,2016 13:51:02
[DHCP IP: (192.168.1.2)] to MAC address A4:67:06:57:DD:0E, Saturday, Apr 16,2016 13:51:02
[Internet disconnected] Saturday, Apr 16,2016 13:51:02
  • IrvSp Per engineering, it needs to sync every hour or so to check the time and connectivity.

5 Replies

  • what exactly is the problem? Most other firmwares from other brands also sync every hour

    • IrvSp's avatar
      IrvSp
      Master

      Not a problem per se. Just that it CHANGED from before, the prior Official F/W (V1.0.4.30) and 2 prior Beta's. Under the last Official F/W and the first beta for this latest F/W it was about every 14 hours, and always had a DISCONNECT a second or so prior to the connect and sync. On the last beta no disconnect showing in the log, and then, somewhere during using that beta the 1 1/2 period started. I am NOT seeing any problems or degradation but all I want to know is 'why?' did it change? Was it my router causing this and possibly a pre-cursor of a router problem, did the NG time server start giving out shorter leases, or something else, like the F/W code changed?

       

      Do you see in the log the time sync and if so, what is the period for sync'ing?

      • ElaineM's avatar
        ElaineM
        NETGEAR Employee Retired

        IrvSp Per engineering, it needs to sync every hour or so to check the time and connectivity.