3 ms·
> 199,180 NTP Client connections from 626 unique IP addresses This seems like an abnormally high connections/IP, even if we assume some of the IPs represent mu
by cmeacham98 6y ago
> 199,180 NTP Client connections from 626 unique IP addresses
This seems like an abnormally high connections/IP, even if we assume some of the IPs represent multiple clients. Perhaps it's because of retrying as the author does not seem to have sent NTP replies back?
- NobodyNada 6y agoThat's over 14 days, so it averages to just under 1 request per IP per hour. That seems reasonable for an NTP server. What seems stranger to me is the incorrect clock settings on 30% of those computers. Why do they all think it's the end of September (even though the years are drastically different)?
- cmeacham98 6y ago> Why do they all think it's the end of September I suspect this is just because the author is sorting the text, and the days at the end of September are lexicographically last given that date formatting.
- fomine3 6y agoThat's why ISO-8601 should be default.
- mminer237 6y agoBut to have your computer bitflip 300 times in a couple weeks is impossible. Either the address is cached incorrectly for a long time or it's just a typo in a config file.
- bibinou 6y agohttps://news.ycombinator.com/item?id=26341576 https://news.ycombinator.com/item?id=26341576
- nucleardog 6y agoGonna wager some sort of cheap IoT/embedded device inappropriately abusing Microsoft’s NTP server with a typo in the configuration.
- Bluecobra 6y agoMy guess is that for some of these clients they made a typo in their ntp.conf file/NTP config but never noticed it was wrong. I have manually configured hosts/devices in the past for a variety of public NTP servers including time.windows.com.