Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 Aug 2023 19:56:42 +0200
From:      Mark Tinka <mark@tinka.africa>
To:        Mailinglists FreeBSD <freebsd-questions@freebsd.org>, FreeBSD Questions List <questions@FreeBSD.org>
Subject:   Re: NTP Sync Issue Across Tata (Europe)
Message-ID:  <bc13e5c6-5c6e-d747-7fcf-a3e18948d1ba@tinka.africa>
In-Reply-To: <1c156201-b9d0-f081-a7b6-272242e80432@tinka.africa>
References:  <1c156201-b9d0-f081-a7b6-272242e80432@tinka.africa>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------UB2fgrKMHxs7IvAPS9rde5zX
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

So looks like https://www.ntppool.org/scores/197.224.66.40 shows that 
this server is not performing optimally.

Whom, at FreeBSD, can I speak to to either fix this or take this server 
out of the pool until connectivity is improved?

Mark.

On 8/5/23 17:43, Mark Tinka wrote:
> Hi all.
>
> I have NTP servers in Europe that are choosing Tata (6453) to get to 
> 0.freebsd.pool.ntp.org which lives on 197.224.66.40:
>
> traceroute -I 0.freebsd.pool.ntp.org
> traceroute to 0.freebsd.pool.ntp.org (197.224.66.40), 64 hops max, 48 
> byte packets
>  1  ae-2-24.er-01-ams.nl.seacomnet.com (105.26.64.13)  0.300 ms 0.301 
> ms  0.215 ms
>  2  ce-0-0-11.cr-01-mrs.fr.seacomnet.com (105.16.8.201)  22.163 ms  
> 22.370 ms  22.084 ms
>  3  ce-0-0-3.br-01-mrs.fr.seacomnet.com (105.16.32.254)  20.230 ms  
> 20.243 ms  20.139 ms
>  4  ix-hge-0-0-0-28.ecore3.emrs2-marseille.as6453.net (80.231.165.52)  
> 21.875 ms  21.679 ms  21.762 ms
>  5  * if-be-3-2.ecore2.emrs2-marseille.as6453.net (195.219.175.0)  
> 42.751 ms *
>  6  if-ae-25-2.tcore1.ldn-london.as6453.net (195.219.175.5) 43.509 ms  
> 43.280 ms  43.353 ms
>  7  195.219.83.158 (195.219.83.158)  203.310 ms  203.452 ms 203.209 ms
>  8  196.20.225.84 (196.20.225.84)  208.289 ms  208.637 ms 208.374 ms
>  9  197.226.230.13 (197.226.230.13)  209.657 ms  209.658 ms 209.830 ms
> 10  197.224.66.40 (197.224.66.40)  208.638 ms  208.632 ms 208.712 ms
>
> NTP is not sync'ing to that address, and sessions stay in an Init state.
>
> Other NTP servers I have in Africa are reaching the same address via 
> local Anycast hosters, and sync'ing just fine.
>
> Anyone else seeing this particular issue across Tata in Europe?
>
> Mark.

--------------UB2fgrKMHxs7IvAPS9rde5zX
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="Tahoma">So looks like
      <a class="moz-txt-link-freetext" href="https://www.ntppool.org/scores/197.224.66.40">https://www.ntppool.org/scores/197.224.66.40</a>; shows that this
      server is not performing optimally.<br>
      <br>
      Whom, at FreeBSD, can I speak to to either fix this or take this
      server out of the pool until connectivity is improved?<br>
      <br>
      Mark.<br>
    </font><br>
    <div class="moz-cite-prefix">On 8/5/23 17:43, Mark Tinka wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:1c156201-b9d0-f081-a7b6-272242e80432@tinka.africa">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <font face="Tahoma">Hi all.<br>
        <br>
        I have NTP servers in Europe that are choosing Tata (6453) to
        get to 0.freebsd.pool.ntp.org which lives on 197.224.66.40:<br>
        <br>
        traceroute -I 0.freebsd.pool.ntp.org<br>
        traceroute to 0.freebsd.pool.ntp.org (197.224.66.40), 64 hops
        max, 48 byte packets<br>
         1  ae-2-24.er-01-ams.nl.seacomnet.com (105.26.64.13)  0.300 ms 
        0.301 ms  0.215 ms<br>
         2  ce-0-0-11.cr-01-mrs.fr.seacomnet.com (105.16.8.201)  22.163
        ms  22.370 ms  22.084 ms<br>
         3  ce-0-0-3.br-01-mrs.fr.seacomnet.com (105.16.32.254)  20.230
        ms  20.243 ms  20.139 ms<br>
         4  ix-hge-0-0-0-28.ecore3.emrs2-marseille.as6453.net
        (80.231.165.52)  21.875 ms  21.679 ms  21.762 ms<br>
         5  * if-be-3-2.ecore2.emrs2-marseille.as6453.net
        (195.219.175.0)  42.751 ms *<br>
         6  if-ae-25-2.tcore1.ldn-london.as6453.net (195.219.175.5) 
        43.509 ms  43.280 ms  43.353 ms<br>
         7  195.219.83.158 (195.219.83.158)  203.310 ms  203.452 ms 
        203.209 ms<br>
         8  196.20.225.84 (196.20.225.84)  208.289 ms  208.637 ms 
        208.374 ms<br>
         9  197.226.230.13 (197.226.230.13)  209.657 ms  209.658 ms 
        209.830 ms<br>
        10  197.224.66.40 (197.224.66.40)  208.638 ms  208.632 ms 
        208.712 ms<br>
        <br>
        NTP is not sync'ing to that address, and sessions stay in an
        Init state.<br>
        <br>
        Other NTP servers I have in Africa are reaching the same address
        via local Anycast hosters, and sync'ing just fine. <br>
        <br>
        Anyone else seeing this particular issue across Tata in Europe?<br>
        <br>
        Mark.<br>
      </font> </blockquote>
    <br>
  </body>
</html>

--------------UB2fgrKMHxs7IvAPS9rde5zX--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bc13e5c6-5c6e-d747-7fcf-a3e18948d1ba>