On Thu, May 7, 2020 at 3:43 PM Watson Ladd via devel <devel@ntpsec.org> wrote: > > On Thu, May 7, 2020 at 4:31 PM Hal Murray via devel <devel@ntpsec.org> wrote: > > > > > > devel@ntpsec.org said: > > > I have upgraded to ntpd ntpsec-1.1.8+ (git rev 36bb89920) and I > > > believe I'm seeing this problem. > > > > You aren't connecting to ntp1.glypnod.com either, so that's probably not a > > cloudflare problem. > > > > Thanks for the report. I may have seen something similar. > > There is speculation and some evidence that port 123 might not work > very well due to ISP interference: I wonder if that might be happening > here.
What I have not seen is an indication that the connection is to port 1234 (as per cloudflares website), any shred of a config file, or usable shred of a log file. For all I know it might be failing to connect to the wrong port. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
