Hi everyone, Blocking Turk Telekom customers/devices from using the pool is an option and if at some point supporting them becomes unsustainable we'll figure out how to do it. As long as we can sustain it, I'd rather we do that.
Obviously getting a contact there who can help would be much much better. Them using the pool is fine, we just need to figure out why they're sending so many requests. Ideally they could add some servers to the pool. Someone from TT tried once, but the routers he added fell over immediately when they were included in the pool. - Blocking isn't as simple as one could hope. We can't just block the NTP requests. We could make the tr zone return no servers or 127.0.0.1 or the example IP addresses, but we don't really know what that will do. Maybe they'll change to use europe.pool.ntp.org instead and then we're even worse off. We could figure out the IP addresses of their DNS servers and block those specifically, but again - it's unpredictable what will happen a few steps down the road. - The job of the NTP Pool is to be the first choice when needing basic NTP service. It's the whole reason we're doing this. Obviously we have to do it in a sustainable way with people contributing servers and in other ways as appropriate, but really remember that the project exists to ensure we have time service for everyone without overloading any particular servers. The corollary here is that we're also the "server of last resort". If they're going to abuse someone, we're likely in the best position to "take it". If we can't at some point we'll figure out to block them, but as long as people are willing to put up their servers to take the load (abuse?), then let's do that. Ask -- Ask Bjørn Hansen, http://askask.com/ _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
