[PR #134] [CLOSED] Improve monitoring script #452

New issue

Closed

opened 2026-03-01 17:25:53 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 17:25:53 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/abh/ntppool/pull/134
Author: @mlichvar
Created: 7/28/2016
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (1)

dffee9f Improve monitoring script

📊 Changes

1 file changed (+3 additions, -4 deletions)

View changed files

📝 monitor (+3 -4)

📄 Description

Check NTP responses if they don't have unsychronized leap and require that the root distance has a reasonable value to ignore servers that would be ignored by some widely used NTP clients (e.g. ntpd using
default tos mindist).

This should affect only a very small number of servers, which for some reason report a large root delay or dispersion, but still have an offset small enough to keep a good score. I think I saw two or three. This check could be useful in case there is a large-scale DoS attack on the pool servers (e.g. exploiting some of the vulnerabilities that were found in ntpd in the past) which would leave them unsynchronized.

This should partially work with net-ntp which doesn't report the fractional part of root dispersion (fixed in abh/net-ntp#2). The check will be just less sensitive, i.e. root dispersion has to reach 2 seconds.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/abh/ntppool/pull/134 **Author:** [@mlichvar](https://github.com/mlichvar) **Created:** 7/28/2016 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`dffee9f`](https://github.com/abh/ntppool/commit/dffee9ffb12dd844a8033dc1e243fe1fc8507e85) Improve monitoring script ### 📊 Changes **1 file changed** (+3 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `monitor` (+3 -4) </details> ### 📄 Description Check NTP responses if they don't have unsychronized leap and require that the root distance has a reasonable value to ignore servers that would be ignored by some widely used NTP clients (e.g. ntpd using default tos mindist). This should affect only a very small number of servers, which for some reason report a large root delay or dispersion, but still have an offset small enough to keep a good score. I think I saw two or three. This check could be useful in case there is a large-scale DoS attack on the pool servers (e.g. exploiting some of the vulnerabilities that were found in ntpd in the past) which would leave them unsynchronized. This should partially work with net-ntp which doesn't report the fractional part of root dispersion (fixed in abh/net-ntp#2). The check will be just less sensitive, i.e. root dispersion has to reach 2 seconds. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>