Hello,
In the new 384.11_2, I have set the option to intercept NTP client requests and enabled the local NTP server.
We recently moved from Eastern (EST) time to Central (CST) time and I have adjusted the timezone on the router to reflect this and even rebooted it. Now locally on the router, when you SSH in and do a date it returns the correct date; however, I have a couple android phones, iphones and windows laptops that all still report getting Eastern Time from an NTP source which I assume is the router since it intercepts requests and is the only DNS entry. I have to override the timezone manually on the devices in order to get them to work.
Has anyone else seen this behavior with the new firmware and is there a way to validate if the local machine is getting its NTP from the router or via the pool.ntp.org directly.
Thanks.
In the new 384.11_2, I have set the option to intercept NTP client requests and enabled the local NTP server.
We recently moved from Eastern (EST) time to Central (CST) time and I have adjusted the timezone on the router to reflect this and even rebooted it. Now locally on the router, when you SSH in and do a date it returns the correct date; however, I have a couple android phones, iphones and windows laptops that all still report getting Eastern Time from an NTP source which I assume is the router since it intercepts requests and is the only DNS entry. I have to override the timezone manually on the devices in order to get them to work.
Has anyone else seen this behavior with the new firmware and is there a way to validate if the local machine is getting its NTP from the router or via the pool.ntp.org directly.
Thanks.