[Bug 201803] [PATCH] etc/ntp.conf to enable pool client functionality

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201803

            Bug ID: 201803
           Summary: [PATCH] etc/ntp.conf to enable pool client
                    functionality
           Product: Base System
           Version: 10.2-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Keywords: patch
          Severity: Affects Many People
          Priority: ---
         Component: conf
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: John.Marshall at riverwillow.com.au
          Keywords: patch

Created attachment 159128
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159128&action=edit
Add pool configuration and dynamic source restrictions

For the past several years, current versions of ntpd have included some very
smart enhancements for using the pool servers. Now, at last, FreeBSD can do
this too. The attached patch enables that functionality.

 1. Replace 'server' statements with 'pool' statements.

'server' configures a PERSISTENT association with a SINGLE server from the IP
addresses returned from the pool DNS name. 'pool' configures PREEMPTIVE
associations with MULTIPLE servers from the IP addresses returned from the pool
DNS name. 'pool' gives us a dynamic set of upstream servers: servers which
become unreliable or unreachable are discarded and new ones configured
automatically from whatever the current set of IP addresses for that pool DNS
name happens to be.

 2. Remove superfluous 'restrict -6' statements.

'restrict' statements which do not include addresses or masks apply to both
IPv4 and IPv6.

 3. Introduce 'restrict source' statement to provide .

'restrict source' provides default restrictions for upstream time servers. When
a new pool server is selected, a new 'restrict' entry will be created for that
server from this template. When a configured server is dropped, its dynamic
'restrict' entry is deleted.

 4. Remove text and examples for discreet server'restrict' statements.

Since explicit server 'restrict' statements are not required with this sample
rc.conf, I suggest that this is superfluous and confusing. I guess it depends
on whether the file is meant to be a tutorial or just a working sample.

 5. Move the local clock 'restrict' sample down to the section dealing with the
local clock.

The following is from a running server (i386 10.2-BETA2 r285783) using the
patched configuration. The patch provided is against stable/10 r285783.

rwsrv02> ntpq -np
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.freebsd.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.004
 1.freebsd.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.004
 2.freebsd.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.004
+125.255.139.115 130.194.1.96     2 u   29  128  377   43.096   -4.175   0.423
*203.23.237.200  203.35.83.242    2 u   32  128  377   29.844   -3.550   0.693
-121.0.0.42      23.31.237.112    3 u   90  256  377   46.560   -2.756   0.850
+54.252.165.245  202.21.137.10    2 u   30  128  377   30.060   -4.859   1.264
-2001:418:3ff::1 204.123.2.72     2 u   43  256  377  173.324   -1.592   1.937
-2001:df0:fe:2:: 130.102.2.123    3 u  242  256  377   44.177    4.080   3.433
-130.102.2.123   216.218.254.202  2 u   27  128  377   46.288   -4.332   0.780
rwsrv02>

-- 
You are receiving this mail because:
You are the assignee for the bug.