On 05/19/2016 06:53 PM, Gonçal Badenes wrote: > Hi Miroslav, and thanks for the very fast reply! > > You are right: the first part is indeed a typo. The correct IP is > 185.132.136.32, but the strange behaviour is anyway there: > > Invalid stratum response from 185.132.136.32 (Your server is in stratum ). Is > your server configured properly? Is public access allowed? If you just > restarted your ntpd, then it might still be stabilizing the timesources - try > again in 10-20 minutes. > > I've been looking at it for days and I cannot find what possibly be the cause > for it. Any help is appreciated. >
I set up a measurement to that address on ripe atlas. 50 nodes, 2 ntp packets every 900 seconds, for ~26 hours. https://atlas.ripe.net/measurements/3805061/#!probes (click time travel, and you can see results for tha past 6 hours or so.) It is reachable from most places, and consistently not reachable from others. It has (almost) consistently bad reachability from the US. 'almost', because I have a server in dallas,texas that can. /Kasper Pedersen _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
