| [chrony-dev] Re: Not working with Cloudflare NTP server |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-dev] Re: Not working with Cloudflare NTP server
- From: Nuno Gonçalves <nunojpg@xxxxxxxxx>
- Date: Mon, 19 Aug 2019 19:43:06 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=Ou8EzcWMGl/odIK4Uz/KZR2B5Jiu7EWOh7eDdhGIlhQ=; b=D5j5S6OvkU4jk/tnxGqJgJene6TZEYiSPpv+/mMo9BL59mPGtdu4awGOCt30WdRUwC fz8C/CLT3c1JRDqRn+tvrvjrwfqIu6Fy78rQZZjTqBRG48XWe8V4F8svNW6zrrQSBeH2 SiS92jl/H9p3yZ5bt7wJBd+p2m92k9sEPE8t3VF+4Xh3nVGj5qGLZYeu3lXg/sKJf7Mi /SxZPQff/NI26YGBws/PIqziFxc4nugpMELYOKEAYaycFRjx+ZZ212bQ6RrksFCDAgAJ 65aH7G//rJ6Bpy1D0lgMG5wxugy6Yekz02h4A5l0ISfg+2gpnktxirgmQ0jFiYu9zJiZ zHdA==
Cloudflare answered to me directly (whitin 5 minutes of the report)
saying that they reject all peer associations and I must use server.
It is correct, it works with server.
Thanks!
On Mon, Aug 19, 2019 at 7:31 PM Nuno Gonçalves <nunojpg@xxxxxxxxx> wrote:
>
> Hi,
>
> I tried to used Cloudflare NTP server at time.cloudflare.com with Chrony.
>
> First we can see it answers:
>
> ➜ ~ ntpdate -q time.cloudflare.com
> server 162.159.200.123, stratum 3, offset -0.002150, delay 0.05771
> server 162.159.200.1, stratum 3, offset -0.002098, delay 0.05699
> 19 Aug 19:27:57 ntpdate[21385]: adjust time server 162.159.200.1
> offset -0.002098 sec
> ➜ ~ ntpdate -q 162.159.200.123
> server 162.159.200.123, stratum 3, offset -0.001873, delay 0.05746
> 19 Aug 19:28:16 ntpdate[21395]: adjust time server 162.159.200.123
> offset -0.001873 sec
>
> To test with chrony I just used a single line on chrony.conf
>
> peer time.cloudflare.com noselect
>
> But chrony failes to talk to this server:
>
> ➜ ~ chronyc sources
> 210 Number of sources = 1
> MS Name/IP address Stratum Poll Reach LastRx Last sample
> ===============================================================================
> =? 162.159.200.123 0 7 0 - +0ns[ +0ns] +/- 0ns
>
> With Chrony compiled with debug info I get:
>
> 2019-08-19T17:22:30Z ntp_core.c:1174:(transmit_timeout) Transmit
> timeout for 162.159.200.123:123
> 2019-08-19T17:22:30Z socket.c:583:(log_message) Sent message to
> 162.159.200.123:123 fd=5 len=48
> 2019-08-19T17:22:30Z socket.c:583:(log_message) Received error message
> to 162.159.200.123 fd=5 len=90 if=2 tss=K
> 2019-08-19T17:22:30Z ntp_io_linux.c:763:(NIO_Linux_ProcessMessage)
> Extracted message for 162.159.200.123:123 fd=5 len=48
> 2019-08-19T17:22:30Z ntp_core.c:2231:(update_tx_timestamp) Updated TX
> timestamp delay=0.000110529
>
> I believe there is some incompability with Cloudflare implementation and Chrony.
>
> Thanks,
> Nuno
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.