NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38. See OrphanModeDev for discussion of this topic.
ntp-4.2.8p9 was released on 21 November 2016. It addresses 1 high- (Windows only), 2 medum-, 2 medum-/low-, and 5 low-severity security issues, 28 bugfixes, and contains other improvements over 4.2.8p8.
Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.
6.2. Orphan mode
Orphan Mode is the stated replacement
for the UndisciplinedLocalClock
. It was added to ntp-4.2.2.
Orphan Mode allows a group of
processes to automonously select a leader in the event that all real time sources become unreachable (i.e. are inaccessible).
Orphan Mode is enabled by adding the line
tos orphan N
specifies the stratum at which this
will switch to Orphan Mode. For example, an
tos orphan 6
will not switch to Orphan Mode as long as a time source of strata 1 through 5 is reachable. The recommended value for
is 2 more than the worst-case externally-reachable source of time.
In addition to the
line all members of the Orphan Mode group must be configured in a mesh
(i.e. they must all be clients / peers of each other). Any NTP association mode may be used to set up this mesh.
NTP versions prior to 4.2.4p5 and 4.2.5p101 will not start up properly in Orphan Mode unless at least one time source is configured in
. If no time sources are specified the
continually increases. This makes these versions unsuitable for use as stand-alone Orphan Mode servers in a time island.
NTP version 4.2.5p101 or later will start up correctly in pure Orphan Mode.
Related Topics: Distribution Documentation: Orphan Mode