Project

General

Profile

Actions
Copy link

Feature #5985

closed

ntp pool command

Added by Derek Schrock over 8 years ago. Updated about 8 years ago.

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

100%

Estimated time:
Plus Target Version:
Release Notes:

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).

Actions
Copy link
 #1

Updated by Jim Thompson over 8 years ago

  • Assignee set to Jim Pingle
  • Target version set to 2.3.1
Actions
Copy link
 #2

Updated by robi robi over 8 years ago

+1 for this

Actions
Copy link
 #3

Updated by Jim Pingle over 8 years 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.

Actions
Copy link
 #4

Updated by Derek Schrock over 8 years 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

Actions
Copy link
 #5

Updated by Chris Buechler over 8 years ago

  • Target version changed from 2.3.1 to 2.3.2
Actions
Copy link
 #6

Updated by Chris Buechler over 8 years ago

  • Target version changed from 2.3.2 to 2.4.0
Actions
Copy link
 #7

Updated by Jim Pingle about 8 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #8

Updated by Jim Pingle about 8 years ago

  • Status changed from Feedback to Resolved

Tested on a few systems, works fine.

Actions
Copy link

Also available in: Atom PDF