From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Migrating from ntp to chrony - challenge
Date: Tue, 06 Jul 2021 15:08:25 +0200
Message-ID: <299e92f1871d570cb46d79c22c3689fd@ipfire.org>
In-Reply-To: <15235E57-D318-41EF-AD45-DA63AD839790@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3879727658387525631=="
List-Id: <development.lists.ipfire.org>

--===============3879727658387525631==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

If you change from ntp keep in mind that we need ntpdate for the settime
skript which is used by unbound to syncronize the time with a given IP
address if the time is incorrect and DNS not working becasue the wrong
time breaks DNSSec.
This is common on system without RTC Battery.

Not sure if chrony can handle this at all.

Arne



Am 2021-06-17 17:26, schrieb Jon Murphy:
> I’d like to challenge!
> 
> (This post was recently moved from the IPFire Community to the
> Development Mailing List)
> 
> I saw this in the agenda from last week:
> 
> Screen Shot 2021-06-16 at 11.42.49 AM1738×500 51.1 KB
> 
> I thought chrony was more for desktops & laptops. Devices that power
> down and might have a big time jump. And NTP was more for servers or
> devices that run full-time.
> 
> The current NTP in IPFire can be easily changed from polling (one per
> hour / once per day) to non-polling by making a few simple changes to
> a config file:
> 
> disable monitor
> restrict default nomodify notrap nopeer
> restrict 127.0.0.1
> server  $NTP_ADDR_1 prefer
> server  $NTP_ADDR_2
> server  127.127.1.0
> fudge   127.127.1.0 stratum 10
> driftfile /etc/ntp/drift
> 
> $NTP_ADDR_1 and _2 are the Primary NTP server and Secondary NTP server
> from the https://ipfire:444/cgi-bin/time.cgi webgui page.
> 
> And by changing the https://ipfire:444/cgi-bin/time.cgi
> Synchronization to Manually
> 
> Anyway, my thought is to make some changes to the current NTP service
> instead of implementing something new…
> 
> Jon
> 
> ---------------------------
> 
> TL;DR
> 
> When NTP is configured differently (Manually polling enabled) it will
> “correct” on it own:
> 
> Oct  6 21:40:01 ipfire ntpdate: Updated drift file.  Drift is 0.000
> PPM at Tue Oct  6 21:35:43 CDT 2020
> Oct  6 23:20:01 ipfire ntpdate: Updated drift file.  Drift is -18.986
> PPM at Tue Oct  6 23:16:05 CDT 2020
> Oct  7 00:20:01 ipfire ntpdate: Updated drift file.  Drift is -140.863
> PPM at Wed Oct  7 00:16:04 CDT 2020
> Oct  7 01:20:01 ipfire ntpdate: Updated drift file.  Drift is -210.676
> PPM at Wed Oct  7 01:16:04 CDT 2020
> Oct  7 02:20:01 ipfire ntpdate: Updated drift file.  Drift is -347.531
> PPM at Wed Oct  7 02:16:04 CDT 2020
> Oct  7 03:20:01 ipfire ntpdate: Updated drift file.  Drift is -407.147
> PPM at Wed Oct  7 03:16:04 CDT 2020
> Oct  7 04:20:01 ipfire ntpdate: Updated drift file.  Drift is -414.606
> PPM at Wed Oct  7 04:16:04 CDT 2020
> Oct  7 05:20:01 ipfire ntpdate: Updated drift file.  Drift is -414.826
> PPM at Wed Oct  7 05:16:04 CDT 2020
> 
> More into:
> 
> https://community.ipfire.org/t/odd-ntp-offset-issues-continued/492

--===============3879727658387525631==--