Re: NTP Sync Issue Across Tata (Europe)

Bill, That still leaves you open to NTP attacks. The USNO accuracy and monitoring is worthless if you suffer, for example, an NTP DDoS attack. [ddos-lc.png] NTP amplification DDoS

Re: NTP Sync Issue Across Tata (Europe)

On Sat, Aug 5, 2023 at 12:26 PM Mel Beckman wrote: > You might consider setting up your own GPS-based NTP network. GPS time is monitored (and when necessary, adjusted) from the U.S. Naval Observatory Master Clock, which is -the- authoritative time source for the United States. The USNO also

Re: NTP Sync Issue Across Tata (Europe)

If the path has simmetric one way latencies you don't have to pick a lower latency faulty one. Perhaps creating a selection at startup and then using that collection ? Rubens Em sáb., 5 de ago. de 2023 12:42, Mark Tinka escreveu: > Hi all. > > I have NTP servers in Europe that are choosing

Re: NTP Sync Issue Across Tata (Europe)

Mark, You might consider setting up your own GPS-based NTP network. Commercial Ethernet GPS-sourced NTP servers, such as the Time Machines, TM1000A, are as little as $400. Or you can roll your own using a Raspberry Pi or similar nano computer with a GPS module and antenna. We use these

Re: NTP Sync Issue Across Tata (Europe)

On 8/5/23 20:17, Chris Adams wrote: It's the NTP pool people you need to talk to - the .freebsd. bit is just a vendored entry into the pool (more for load tracking and management). Yes, Andreas clarified in unicast. Will do. Thanks. Mark.

Re: NTP Sync Issue Across Tata (Europe)

Once upon a time, Mark Tinka said: > On 8/5/23 19:51, Andreas Ott wrote: > >See for yourself how his pool server scores at > >https://www.ntppool.org/scores/197.224.66.40 > > > >I am not sure why it would be inserted into DNS answers for a > >worldwide pool like 0.freebsd as it clearly does have

Re: NTP Sync Issue Across Tata (Europe)

On 8/5/23 19:51, Andreas Ott wrote: See for yourself how his pool server scores at https://www.ntppool.org/scores/197.224.66.40 I am not sure why it would be inserted into DNS answers for a worldwide pool like 0.freebsd as it clearly does have connectivity issues from some of the pool

Re: NTP Sync Issue Across Tata (Europe)

See for yourself how his pool server scores at https://www.ntppool.org/scores/197.224.66.40 I am not sure why it would be inserted into DNS answers for a worldwide pool like 0.freebsd as it clearly does have connectivity issues from some of the pool project's own sensors. -andreas On Sat, Aug 5,

Re: NTP Sync Issue Across Tata (Europe)

On 8/5/23 18:30, Matthew McGehrin wrote: Hi Mark. Wouldn't a local server be more optimal? IE: server 0.nl.pool.ntp.org server 1.nl.pool.ntp.org server 2.nl.pool.ntp.org server 3.nl.pool.ntp.org I have a bunch of servers all over Europe I'd

Re: NTP Sync Issue Across Tata (Europe)

Hi Mark. Wouldn't a local server be more optimal? IE: server 0.nl.pool.ntp.org server 1.nl.pool.ntp.org server 2.nl.pool.ntp.org server 3.nl.pool.ntp.org Or for Africa server 0.za.pool.ntp.org server 1.za.pool.ntp.org server

NTP Sync Issue Across Tata (Europe)

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