Orbi WiFi 7 RBE973
Reply

Re: NTP Time Broke

TomBlack
Guide

NTP Time Broke

V1.0.11.128_10.2.112

 

NTP set to GMT -5.  When the Router sends a log file, the time is off by 5 hours.

 

The email is time stamped:  

[email sent to: Tom.Black@Comcast.net] Thursday, Dec 30,2021 03:01:03 

 

It should say 8:00 am.  I have the Router set to send me Daily Logs @ 8 am local time which is GMT -5.  This never used to be an issue, so somehow it got broke. 

 

 

Model: R7000P|Nighthawk AC2300 Smart WiFi Dual Band Gigabit Router
Message 1 of 9
schumaku
Guru

Re: NTP Time Broke


@TomBlack wrote:

V1.0.11.128_10.2.112 


Reads more like e.g. an R7000, not an R7000P as tagged.

 


@TomBlack wrote:

NTP set to GMT -5.  When the Router sends a log file, the time is off by 5 hours.

 

The email is time stamped:  

[email sent to: Tom.Black@Comcast.net] Thursday, Dec 30,2021 03:01:03 

 

It should say 8:00 am.  I have the Router set to send me Daily Logs @ 8 am local time which is GMT -5.  This never used to be an issue, so somehow it got broke. 


Ref. the subjet "NTP Time Broke" you can check the time zone and local time currently set in place on the router itself.

 

The issue itself seems to related more to the schedule or how the schedule is set in place. Was the NTP time set probably delayed? Does rebooting change this issue on the next morning? 

 

@plemans or @microchip8 - any idea what seems to go wrong there, probably since the V1.0.11.128_10.2.112 update?;

Message 2 of 9
TomBlack
Guide

Re: NTP Time Broke

I updated Firmware from R7000-V1.0.9.88_10.2.88.  Had no NTP issues with this Firmware.  NTP issue started with the latest Firmware previously noted V1.0.11.128_10.2.112.

 

The R7000 Router shows the correct time on the NTP screen and is repeatable even after a Router Reboot.  It's the Send Email Function that is NOT reading the NTP time correctly.  It's showing GMT instead of GMT -5 that is set in the Router NTP Screen.

Model: R7000|AC1900 Smart WIFI Router
Message 3 of 9
plemans
Guru

Re: NTP Time Broke

Since I was tagged, not a clue 🙂

I rarely setup any logging with emailed responses and I don't have that specific device to test it on. 

Sorry. 

Message 4 of 9
schumaku
Guru

Re: NTP Time Broke


@TomBlack wrote:

I updated Firmware from R7000-V1.0.9.88_10.2.88.  Had no NTP issues with this Firmware.  NTP issue started with the latest Firmware previously noted V1.0.11.128_10.2.112.


Understand.

 


@TomBlack wrote:

The R7000 Router shows the correct time on the NTP screen and is repeatable even after a Router Reboot.


OK.

 


@TomBlack wrote:

It's the Send Email Function that is NOT reading the NTP time correctly.  It's showing GMT instead of GMT -5 that is set in the Router NTP Screen.


Does this mean the email is generated and sent five hours to early? At 03:00 local instead of 08:00 local as configured? This would indicate the scheduler isn't properly working on the local configured time zone.

 

Or is the report generated on the scheduled time, but the SMTP header isn't correct? This option I would exclude due to the log entry shown above.

 

This is all unrelated to NTP - because the NTP time is _always_ exchanged in GMT (Zulu time). Displayed in the Web UI is the local time, adjusted by the time zone configured.

 

Don't be confused that the email programs are adjusting the displayed time based on the SMTP header information - this part (the complete SMTP header) would be interesting to proof in fact.

 

 

Message 5 of 9
TomBlack
Guide

Re: NTP Time Broke

Does this mean the email is generated and sent five hours to early? At 03:00 local instead of 08:00 local as configured? This would indicate the scheduler isn't properly working on the local configured time zone.

 

> Yes, have had several Log Emails sent @ 3 am local instead of 8 am (GMT -5).

 

Or is the report generated on the scheduled time, but the SMTP header isn't correct? This option I would exclude due to the log entry shown above.

 

> Yes, have had several sent at the correct time, but the email header showed 3 am.  The Router is generating the Header, yes?

Message 6 of 9
schumaku
Guru

Re: NTP Time Broke

Now you have confused me once more.

 


@TomBlack wrote:

Does this mean the email is generated and sent five hours to early? At 03:00 local instead of 08:00 local as configured? This would indicate the scheduler isn't properly working on the local configured time zone.

 

> Yes, have had several Log Emails sent @ 3 am local instead of 8 am (GMT -5).


So this is the "new" case since the recent update?

 


@TomBlack wrote:

Or is the report generated on the scheduled time, but the SMTP header isn't correct? This option I would exclude due to the log entry shown above.

 

> Yes, have had several sent at the correct time, but the email header showed 3 am.  The Router is generating the Header, yes?


Yes, of course, the simple sendmail does start with the header generation.

 

Can't say much more here on the R7000 and the latest firmware. Had spent reasonable time on the R9000 and found certain oddities, where I tend to state it's kind of a Netgear router "standard". While we have the time and time zone correctly configured, the system and the shell does still claim run on GMT, but showing the local time (while a "real" Linux system does make it different, read: Correct). The environment variables of course are showing the effecive time zone, while checking the time on the shell shows GMT, but the local time. This requires certain code changes, being for the scheduler, the simple sendmail, and several more ... to make them believe they operate in the effective time zone. That's why I don't wonder to much that certain code updates lead to these kind of odd issues. I made to much noise abut that, and as a result Netgear removed the ability to enable the telnet access in response to my nagging. 

Message 7 of 9
TomBlack
Guide

Re: NTP Time Broke

The latest Firmware shows the correct GMT -5 time on the screen, but the Firmware sends out a Daily Log at 3am (GMT) instead of 8am (GMT -5) daily and continues to do so.  There is a bug in the latest Firmware.  I have restarted the Router several times to no avail.

 

Here is the last Log Entry for this morning:  

[email sent to: Tom.XXXXX@XXXXXXXXXXX] Friday, Jan 07,2022 03:01:08

 

Please note the email was sent 5 hours early as confirmed by the Router.

 

Again, prior Firmware versions did not have this issue.

Model: R7000|AC1900 Smart WIFI Router
Message 8 of 9
TomBlack
Guide

Re: NTP Time Broke

This issue still present in Firmware 1.0.11.130.  NTP time is correct, but the daily log is sent 5 hours too early.

 

[Admin login] from source 192.168.5.2, Monday, Jan 17,2022 11:07:12

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 11:06:58

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 10:58:29

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 10:57:47

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 10:52:52

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 10:52:19

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 10:48:45

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 10:47:59

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 10:44:44

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 10:43:06

[DHCP IP: (192.168.5.60)] to MAC address 44:94:FC:6E:44:F4, Monday, Jan 17,2022 07:00:36

[DHCP IP: (192.168.5.2)] to MAC address 10:BF:48:BA:EF:7B, Monday, Jan 17,2022 07:00:33

[DHCP IP: (192.168.5.70)] to MAC address B0:B9:8A:43:39:E4, Monday, Jan 17,2022 07:00:33

[email sent to: xxx@xxx] Monday, Jan 17,2022 03:01:01

^^^^^^^^

5 Hours Too Soon!  Email is sent @ GMT; not GMT -5 like the Router Time is set to.

 

Model: R7000|AC1900 Smart WIFI Router
Message 9 of 9
Top Contributors
Discussion stats
  • 8 replies
  • 1082 views
  • 0 kudos
  • 3 in conversation
Announcements

Orbi WiFi 7