Project

General

Profile

Feature #5985

ntp pool command

Added by Derek Schrock about 1 year ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
NTPD
Target version:
Start date:
03/12/2016
Due date:
% Done:

100%


Description

For future ntp (FreeBSD 10.2+ ntpd 4.2.8p3) usage would it be possible for the web interface to support the pool command (http://doc.ntp.org/4.2.6/manyopt.html#pool)?

Setting multiple servers you run the risk of them not being valid time sources. This is partially mitigated if you're using hosts from the ntp.org's pool project however all to this would go away if you use the pool command.

With ntpd's pool the client's maxclock will be used to set the number of possible peers and bad peers will be rotated out as needed with a since pool line in ntp.conf (https://www.freebsd.org/cgi/man.cgi?query=ntp.conf&sektion=5).

Associated revisions

Revision fbb652ed
Added by Jim Pingle 5 months ago

Use the ntpd "pool" command for more robust timekeeping. Attempting to automatically determine if we are using a pool, and allow it to be set optionally otherwise. Implements #5985

History

#1 Updated by Jim Thompson about 1 year ago

  • Assignee set to Jim Pingle
  • Target version set to 2.3.1

#2 Updated by robi robi 12 months ago

+1 for this

#3 Updated by Jim Pingle 12 months ago

I've tried this manually and couldn't get any working result from it. Does anyone happen to have a working example of an ntp config with the pool command working as they expect, for comparison?

ntpd accepted the directive but it never did sync up with anything when I tried.

#4 Updated by Derek Schrock 12 months ago

Jim Pingle wrote:

I've tried this manually and couldn't get any working result from it. Does anyone happen to have a working example of an ntp config with the pool command working as they expect, for comparison?

ntpd accepted the directive but it never did sync up with anything when I tried.

You need to add an extra restrict line for pool:

From my ntp.conf:

...
restrict source limited kod
...

You can find the reasoning here http://lists.ntp.org/pipermail/questions/2010-April/026304.html

#5 Updated by Chris Buechler 11 months ago

  • Target version changed from 2.3.1 to 2.3.2

#6 Updated by Chris Buechler 9 months ago

  • Target version changed from 2.3.2 to 2.4.0

#7 Updated by Jim Pingle 5 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#8 Updated by Jim Pingle 5 months ago

  • Status changed from Feedback to Resolved

Tested on a few systems, works fine.

Also available in: Atom PDF