freebsd-nq/usr.sbin/xntpd/doc/xntpdc.8

675 lines
21 KiB
Groff
Raw Normal View History

1998-02-19 08:05:46 +00:00
.\"
1999-08-28 01:35:59 +00:00
.\" $FreeBSD$
1998-02-19 08:05:46 +00:00
.\"
.Dd December 21, 1993
.Dt XNTPDC 8
.Os
.Sh NAME
.Nm xntpdc
.Nd query/control program for the Network Time Protocol daemon
.Sh SYNOPSIS
.Nm xntpdc
.Op Fl ilnps
.Op Fl c Ar command
.Op Ar host ...
.Sh DESCRIPTION
.Nm Xntpdc
1993-12-21 18:36:48 +00:00
is used to query the
1998-02-19 08:05:46 +00:00
.Xr xntpd 8
1994-09-29 23:04:24 +00:00
daemon about its current state and to request changes in that state. The
1993-12-21 18:36:48 +00:00
program may be run either in interactive mode or controlled using
1994-09-29 23:04:24 +00:00
command line arguments. Extensive state and statistics information is
1993-12-21 18:36:48 +00:00
available through the
1998-02-19 08:05:46 +00:00
.Nm
1994-09-29 23:04:24 +00:00
interface. In addition, nearly all the configuration options which can
1993-12-21 18:36:48 +00:00
be specified at start up using
1998-02-19 08:05:46 +00:00
.Nm xntpd Ns 's
1993-12-21 18:36:48 +00:00
configuration file may also be specified at run time using
1998-02-19 08:05:46 +00:00
.Nm Ns .
.Pp
1993-12-21 18:36:48 +00:00
If one or more request options is included on the command line when
1998-02-19 08:05:46 +00:00
.Nm
is executed, each of the requests will be sent to the
.Tn NTP
servers
1994-09-29 23:04:24 +00:00
running on each of the hosts given as command line arguments, or on
1998-02-19 08:05:46 +00:00
.Ar localhost
1994-09-29 23:04:24 +00:00
by default. If no request options are given,
1998-02-19 08:05:46 +00:00
.Nm
1993-12-21 18:36:48 +00:00
will attempt to read commands from the standard input and execute these
1998-02-19 08:05:46 +00:00
on the
.Tn NTP
server running on the first host given on the command line,
1994-09-29 23:04:24 +00:00
again defaulting to
1998-02-19 08:05:46 +00:00
.Ar localhost
1993-12-21 18:36:48 +00:00
when no other host is specified.
1998-02-19 08:05:46 +00:00
.Nm Xntpdc
1993-12-21 18:36:48 +00:00
will prompt for commands if the standard input is a terminal device.
1998-02-19 08:05:46 +00:00
.Pp
.Nm Xntpdc
uses
.Tn NTP
mode 7 packets to communicate with the
.Tn NTP
server, and hence
1993-12-21 18:36:48 +00:00
can be used to query any compatable server on the network which permits
1998-02-19 08:05:46 +00:00
it. Note that since
.Tn NTP
is a UDP protocol this communication will be
1993-12-21 18:36:48 +00:00
somewhat unreliable, especially over large distances in terms of network
topology.
1998-02-19 08:05:46 +00:00
.Nm Xntpdc
1993-12-21 18:36:48 +00:00
makes no attempt to retransmit requests, and will time requests out if
the remote host is not heard from within a suitable time out time.
1998-02-19 08:05:46 +00:00
.Pp
1994-09-29 23:04:24 +00:00
Command line options are described following. Specifying a command line
option other than
1998-02-19 08:05:46 +00:00
.Fl i
1993-12-21 18:36:48 +00:00
or
1998-02-19 08:05:46 +00:00
.Fl n
1993-12-21 18:36:48 +00:00
will cause the specified query (queries) to be sent to the indicated
1994-09-29 23:04:24 +00:00
host(s) immediately. Otherwise,
1998-02-19 08:05:46 +00:00
.Nm
1994-09-29 23:04:24 +00:00
will attempt to read interactive format commands from the standard
input.
1998-02-19 08:05:46 +00:00
.Bl -tag -width indent
.It Fl c
1993-12-21 18:36:48 +00:00
The following argument is interpreted as an interactive format command
and is added to the list of commands to be executed on the specified
1994-09-29 23:04:24 +00:00
host(s). Multiple
1998-02-19 08:05:46 +00:00
.Fl c
1993-12-21 18:36:48 +00:00
options may be given.
1998-02-19 08:05:46 +00:00
.It Fl i
1993-12-21 18:36:48 +00:00
Force
1998-02-19 08:05:46 +00:00
.Nm
1994-09-29 23:04:24 +00:00
to operate in interactive mode. Prompts will be written to the standard
output and commands read from the standard input.
1998-02-19 08:05:46 +00:00
.It Fl l
1994-09-29 23:04:24 +00:00
Obtain a list of peers which are known to the server(s). This switch is
1998-02-19 08:05:46 +00:00
equivalent to
.Qq -c listpeers .
.It Fl n
1993-12-21 18:36:48 +00:00
Output all host addresses in dotted\-quad numeric format rather than
converting to the canonical host names.
1998-02-19 08:05:46 +00:00
.It Fl p
1994-09-29 23:04:24 +00:00
Print a list of the peers known to the server as well as a summary of
1998-02-19 08:05:46 +00:00
their state. This is equivalent to
.Qq -c peers .
.It Fl s
1994-09-29 23:04:24 +00:00
Print a list of the peers known to the server as well as a summary of
their state, but in a slightly different format than the
1998-02-19 08:05:46 +00:00
.Fl p
switch. This is equivalent to
.Qq -c dmpeers .
.El
.Sh INTERNAL COMMANDS
1994-09-29 23:04:24 +00:00
Interactive format commands consist of a keyword followed by zero to
four arguments. Only enough characters of the full keyword to uniquely
identify the command need be typed. The output of a command is normally
sent to the standard output, but optionally the output of individual
1998-02-19 08:05:46 +00:00
commands may be sent to a file by appending a
.Qq > ,
followed by a
1994-09-29 23:04:24 +00:00
file name, to the command line.
1998-02-19 08:05:46 +00:00
.Pp
1993-12-21 18:36:48 +00:00
A number of interactive format commands are executed entirely within the
1998-02-19 08:05:46 +00:00
.Nm
program itself and do not result in
.Tn NTP
mode 7 requests being sent to a
server. These are described following:
.Pp
.Bl -tag -width indent
.It Xo ?
.Op Ar command_keyword
.Xc
A
.Em ?
by itself will print a list of all the command keywords
1993-12-21 18:36:48 +00:00
known to this incarnation of
1998-02-19 08:05:46 +00:00
.Nm Ns .
A
.Em ?
followed by a command keyword will print function and
1994-09-29 23:04:24 +00:00
usage information about the command. This command is probably a better
1993-12-21 18:36:48 +00:00
source of information about
1998-02-19 08:05:46 +00:00
.Nm
1993-12-21 18:36:48 +00:00
than this manual page.
1998-02-19 08:05:46 +00:00
.It help Ar command_keyword
1993-12-21 18:36:48 +00:00
A synonym for the
1998-02-19 08:05:46 +00:00
.Em ?
1993-12-21 18:36:48 +00:00
command.
1998-02-19 08:05:46 +00:00
.It timeout Ar millseconds
1994-09-29 23:04:24 +00:00
Specify a time out period for responses to server queries. The default
1993-12-21 18:36:48 +00:00
is about 8000 milliseconds.
1998-02-19 08:05:46 +00:00
.It delay Ar milliseconds
1993-12-21 18:36:48 +00:00
Specify a time interval to be added to timestamps included in requests
1994-09-29 23:04:24 +00:00
which require authentication. This is used to enable (unreliable) server
1993-12-21 18:36:48 +00:00
reconfiguration over long delay network paths or between machines whose
clocks are unsynchronized.
1998-02-19 08:05:46 +00:00
.It host Ar hostname
1993-12-21 18:36:48 +00:00
Set the host to which future queries will be sent.
1998-02-19 08:05:46 +00:00
.Ar Hostname
1994-09-29 23:04:24 +00:00
may be either a host name or a numeric (dotted quad) dmaddress.
1998-02-19 08:05:46 +00:00
.It keyid Ar #
1993-12-21 18:36:48 +00:00
This command allows the specification of a key number to be used to
1994-09-29 23:04:24 +00:00
authenticate configuration requests. This must correspond to the key
number the server has been configured to use for this purpose.
1998-02-19 08:05:46 +00:00
.It passwd
1993-12-21 18:36:48 +00:00
This command prompts you to type in a password (which will not be
1994-09-29 23:04:24 +00:00
echoed) which will be used to authenticate configuration requests. The
1998-02-19 08:05:46 +00:00
password must correspond to the key configured for use by the
.Tn NTP
server for this purpose if such requests are to be successful.
.It hostnames Ar yes|no
If
.Ar yes
is specified, host names are printed in information
displays. If
.Ar no
is given, numeric addresses are printed
instead. The default is
.Ar yes
unless modified using the command line
.Fl n
1993-12-21 18:36:48 +00:00
switch.
1998-02-19 08:05:46 +00:00
.It quit
1993-12-21 18:36:48 +00:00
Exit
1998-02-19 08:05:46 +00:00
.Nm Ns .
.El
.Sh QUERY COMMANDS
Query commands result in
.Tn NTP
mode 7 packets containing requests for
information being sent to the server. These are
.Qq read\-only
1993-12-21 18:36:48 +00:00
commands in that they make no modification of the server configuration
state.
1998-02-19 08:05:46 +00:00
.Bl -tag -width indent
.It listpeers
Obtain and print a brief list of the peers for which the server is
1994-09-29 23:04:24 +00:00
maintaining state. These should include all configured peer associations
as well as those peers whose stratum is such that they are considered by
1998-02-19 08:05:46 +00:00
the server to be possible future synchronization candidates.
.It peers
Obtain a list of peers for which the server is maintaining state, along
1994-09-29 23:04:24 +00:00
with a summary of that state. Summary information includes the address
of the remote peer, the local interface address (0.0.0.0 if a local
address has yet to be determined), the stratum of the remote peer (a
stratum of 16 indicates the remote peer is unsynchronized), the polling
interval, in seconds, the reachability register, in octal, and the
current estimated delay, offset and dispersion of the peer, all in
seconds. In addition, the character in the left margin indicates the
1998-02-19 08:05:46 +00:00
mode this peer entry is operating in. A
.Qq +
denotes symmetric
active, a
.Qq -
indicates symmetric passive, a
.Qq =
means
the remote server is being polled in client mode, a
.Qq ^
indicates that the server is broadcasting to this address, a
.Qq ~
denotes that the remote peer is sending broadcasts and a
.Qq *
marks the peer the server is currently synchronizing to.
.Pp
1994-09-29 23:04:24 +00:00
The contents of the host field may be one of four forms. It may be a
host name, an IP address, a reference clock implementation name with its
1998-02-19 08:05:46 +00:00
parameter or
.Qq REFCLK(<implementation number>, <parameter>) .
On
.Qq hostnames no
only IP\-addresses will be displayed.
.It dmpeers
1994-09-29 23:04:24 +00:00
A slightly different peer summary list. Identical to the output of the
1998-02-19 08:05:46 +00:00
.Em peers
1994-09-29 23:04:24 +00:00
command except for the character in the leftmost column. Characters only
appear beside peers which were included in the final stage of the clock
1998-02-19 08:05:46 +00:00
selection algorithm. A
.Qq \&.
indicates that this peer was cast off
in the falseticker detection, while a
.Qq +
indicates that the
peer made it through. A
.Qq *
denotes the peer the server is
1994-09-29 23:04:24 +00:00
currently synchronizing with.
1998-02-19 08:05:46 +00:00
.It Xo showpeer
.Ar peer_address
.Op Ar addr2
.Op Ar addr3
.Op Ar addr4
.Xc
Show a detailed display of the current peer variables for one or more
peers. Most of these values are described in the
.Tn NTP
Version 2 specification.
.It Xo pstats
.Ar peer_address
.Op Ar addr2
.Op Ar addr3
.Op Ar addr4
.Xc
1993-12-21 18:36:48 +00:00
Show per\-peer statistic counters associated with the specified peer(s).
1998-02-19 08:05:46 +00:00
.It Xo clockinfo
.Ar clock_peer_address
.Op Ar addr2
.Op Ar addr3
.Op Ar addr4
.Xc
1994-09-29 23:04:24 +00:00
Obtain and print information concerning a peer clock. The values
obtained provide information on the setting of fudge factors and other
clock performance information.
1998-02-19 08:05:46 +00:00
.It kerninfo
1994-09-29 23:04:24 +00:00
Obtain and print kernel phase-lock loop operating parameters. This
information is available only if the kernel has been specially modified
for a precision timekeeping function.
1998-02-19 08:05:46 +00:00
.It loopinfo Op Ar oneline|multiline
1994-09-29 23:04:24 +00:00
Print the values of selected loop filter variables. The loop filter is
1998-02-19 08:05:46 +00:00
the part of
.Tn NTP
which deals with adjusting the local system clock. The
.Qq offset
is the last offset given to the loop filter by the
packet processing code. The
.Qq frequency
is the frequency error
of the local clock in parts-per-million (ppm). The
.Qq time_const
controls the
.Qq stiffness
of the phase-lock loop and thus the speed at
which it can adapt to oscillator drift. The
.Qq watchdog timer
1994-09-29 23:04:24 +00:00
value is the number of seconds which have elapsed since the last sample
1998-02-19 08:05:46 +00:00
offset was given to the loop filter. The
.Ar oneline
and
.Ar multiline
options specify the format in which this information
is to be printed, with
.Ar multiline
as the default.
.It sysinfo
1993-12-21 18:36:48 +00:00
Print a variety of system state variables, i.e. state related to the
1998-02-19 08:05:46 +00:00
local server. All except the last four lines are described in the
.Tn NTP
Version 3 specification, RFC 1305. The
.Qq system flags
show various system flags, some of which can be set and cleared by the
.Qq enable
and
.Qq disable
configuration commands,
respectively. The
.Qq stability
is the residual frequency error
1994-09-29 23:04:24 +00:00
remaining after the system frequency correction is applied and is
intended for maintenance and debugging. In most architectures, this
value will initially decrease from as high as 500 ppm to a nominal value
in the range .01 to 0.1 ppm. If it remains high for some time after
starting the daemon, something may be wrong with the local clock, or the
1998-02-19 08:05:46 +00:00
value of the kernel variable
.Qq tick
may be incorrect. The
.Qq broadcastdelay
shows the default broadcast delay, as set by
the
.Qq broadcastdelay
configuration command, while the
.Qq authdelay
shows the default authentication delay, as set by
the
.Qq authdelay
configuration command.
.It sysstats
1994-09-29 23:04:24 +00:00
Print statistics counters maintained in the protocol module.
1998-02-19 08:05:46 +00:00
.It memstats
1994-09-29 23:04:24 +00:00
Print statistics counters related to memory allocation
1993-12-21 18:36:48 +00:00
code.
1998-02-19 08:05:46 +00:00
.It iostats
1994-09-29 23:04:24 +00:00
Print statistics counters maintained in the input\-output module.
1998-02-19 08:05:46 +00:00
.It timerstats
1994-09-29 23:04:24 +00:00
Print statistics counters maintained in the timer/event queue support
code.
1998-02-19 08:05:46 +00:00
.It reslist
1994-09-29 23:04:24 +00:00
Obtain and print the server's restriction list. This list is (usually)
1993-12-21 18:36:48 +00:00
printed in sorted order and may help to understand how the restrictions
are applied.
1998-02-19 08:05:46 +00:00
.It monlist Op Ar version
1994-09-29 23:04:24 +00:00
Obtain and print traffic counts collected and maintained by the monitor
facility. The version number should not normally need to be specified.
1998-02-19 08:05:46 +00:00
.It Xo clkbug
.Ar clock_peer_address
.Op Ar addr2
.Op Ar addr3
.Op Ar addr4
.Xc
1994-09-29 23:04:24 +00:00
Obtain debugging information for a reference clock driver. This
information is provided only by some clock drivers and is mostly
undecodable without a copy of the driver source in hand.
1998-02-19 08:05:46 +00:00
.El
.Sh RUNTIME CONFIGURATION REQUESTS
1993-12-21 18:36:48 +00:00
All requests which cause state changes in the server are authenticated
1998-02-19 08:05:46 +00:00
by the server using a configured
.Tn NTP
key (the facility can also be
1994-09-29 23:04:24 +00:00
disabled by the server by not configuring a key). The key number and the
corresponding key must also be made known to
1998-02-19 08:05:46 +00:00
.Nm Ns .
1993-12-21 18:36:48 +00:00
This can be done using the
1998-02-19 08:05:46 +00:00
.Em keyid
1993-12-21 18:36:48 +00:00
and
1998-02-19 08:05:46 +00:00
.Em passwd
1994-09-29 23:04:24 +00:00
commands, the latter of which will prompt at the terminal for a password
to use as the encryption key. You will also be prompted automatically
for both the key number and password the first time a command which
would result in an authenticated request to the server is given.
Authentication not only provides verification that the requester has
permission to make such changes, but also gives an extra degree of
protection again transmission errors.
1998-02-19 08:05:46 +00:00
.Pp
1994-09-29 23:04:24 +00:00
Authenticated requests always include a timestamp in the packet data,
which is included in the computation of the authentication code. This
timestamp is compared by the server to its receive time stamp. If they
differ by more than a small amount the request is rejected. This is done
for two reasons. First, it makes simple replay attacks on the server, by
someone who might be able to overhear traffic on your LAN, much more
difficult. Second, it makes it more difficult to request configuration
changes to your server from topologically remote hosts. While the
reconfiguration facility will work well with a server on the local host,
and may work adequately between time\-synchronized hosts on the same
LAN, it will work very poorly for more distant hosts. As such, if
reasonable passwords are chosen, care is taken in the distribution and
protection of keys and appropriate source address restrictions are
applied, the run time reconfiguration facility should provide an
adequate level of security.
1998-02-19 08:05:46 +00:00
.Pp
The following commands all make authenticated requests:
.Bl -tag -width indent
.It Xo addpeer
.Ar peer_address
.Op Ar keyid
.Op Ar version#
.Op Ar prefer
.Xc
1994-09-29 23:04:24 +00:00
Add a configured peer association at the given address and operating in
symmetric active mode. Note that an existing association with the same
peer may be deleted when this command is executed, or may simply be
converted to conform to the new configuration, as appropriate. If the
1998-02-19 08:05:46 +00:00
optional
.Ar keyid
is a nonzero integer, all outgoing packets to
1994-09-29 23:04:24 +00:00
the remote server will have an authentication field attached encrypted
with this key. If the value is 0 (or not given) no authentication will
1998-02-19 08:05:46 +00:00
be done. The
.Ar version#
can be 1, 2 or 3 and defaults to 3. The
.Ar prefer
keyword indicates a preferred peer (and thus will be
1994-09-29 23:04:24 +00:00
used primarily for clock synchronisation if possible). The preferred
peer also determines the validity of the PPS signal - if the preferred
peer is suitable for synchronisation so is the PPS signal.
1998-02-19 08:05:46 +00:00
.It Xo addserver
.Ar peer_address
.Op Ar keyid
.Op Ar version#
.Op Ar prefer
.Xc
1993-12-21 18:36:48 +00:00
Identical to the
1998-02-19 08:05:46 +00:00
.Em addpeer
1994-09-29 23:04:24 +00:00
command, except that the operating mode is client.
1998-02-19 08:05:46 +00:00
.It Xo broadcast
.Ar peer_address
.Op Ar keyid
.Op Ar version#
.Xc
1993-12-21 18:36:48 +00:00
Identical to the
1998-02-19 08:05:46 +00:00
.Em addpeer
1994-09-29 23:04:24 +00:00
command, except that the operating mode is broadcast. In this case a
1998-02-19 08:05:46 +00:00
valid key identifier and key are required. The
.Ar peer_address
1994-09-29 23:04:24 +00:00
parameter can be the broadcast address of the local network or a
1998-02-19 08:05:46 +00:00
multicast group address assigned to
.Tn NTP .
If a multicast address, a
1994-09-29 23:04:24 +00:00
multicast-capable kernel is required.
1998-02-19 08:05:46 +00:00
.It Xo unconfig
.Ar peer_address
.Op Ar addr2
.Op Ar addr3
.Op Ar addr4
.Xc
1993-12-21 18:36:48 +00:00
This command causes the configured bit to be removed from the specified
1994-09-29 23:04:24 +00:00
peer(s). In many cases this will cause the peer association to be
deleted. When appropriate, however, the association may persist in an
unconfigured mode if the remote peer is willing to continue on in this
fashion.
1998-02-19 08:05:46 +00:00
.It Xo fudge
.Ar peer_address
.Op Ar time1
.Op Ar time2
.Op Ar stratum
.Op Ar refid
.Xc
1994-09-29 23:04:24 +00:00
This command provides a way to set certain data for a reference clock.
See the source listing for further information.
1998-02-19 08:05:46 +00:00
.It Xo enable
.Ar auth|bclient|pll|monitor|stats
.Op Ar ...
.Xc
Provide a way to enable various server options. Flags not mentioned are
unaffected. The
.Ar auth
flag causes the server to synchronize
1994-09-29 23:04:24 +00:00
with unconfigured peers only if the peer has been correctly
authenticated using a trusted key and key identifier. The default for
1998-02-19 08:05:46 +00:00
this flag is disable (off). The
.Ar bclient
flag causes the server
1994-09-29 23:04:24 +00:00
to listen for a message from a broadcast or multicast server, following
which an association is automatically instantiated for that server. The
1998-02-19 08:05:46 +00:00
default for this flag is disable (off). The
.Ar pll
flag enables
1994-09-29 23:04:24 +00:00
the server to adjust its local clock, with default enable (on). If not
set, the local clock free-runs at its intrinsic time and frequency
offset. This flag is useful in case the local clock is controlled by
1998-02-19 08:05:46 +00:00
some other device or protocol and
.Tn NTP
is used only to provide
synchronization to other clients. The
.Ar monitor
flag enables the
1994-09-29 23:04:24 +00:00
monitoring facility (see elsewhere), with default disable (off). The
1998-02-19 08:05:46 +00:00
.Ar stats
flag enables statistics facility filegen (see
1994-09-29 23:04:24 +00:00
description elsewhere.), with default enable (on).
1998-02-19 08:05:46 +00:00
.It Xo disable
.Ar auth|bclient|pll|monitor|stats
.Op Ar ...
.Xc
Provide a way to disable various server options. Flags not mentioned
1994-09-29 23:04:24 +00:00
are unaffected. The flags presently available are described under the
enable command.
1998-02-19 08:05:46 +00:00
.It Xo restrict
.Ar address
.Ar mask
.Ar flag
.Op Ar flag
.Xc
Cause flag(s) to be added to an existing restrict list entry, or adds a
1994-09-29 23:04:24 +00:00
new entry to the list with the specified flag(s). The possible choices
1993-12-21 18:36:48 +00:00
for the flags arguments are given in the following list:
1998-02-19 08:05:46 +00:00
.Bl -tag -width indent
.It ignore
1994-09-29 23:04:24 +00:00
Ignore all packets from hosts which match this entry. If this flag is
specified neither queries nor time server polls will be responded to.
1998-02-19 08:05:46 +00:00
.It noquery
Ignore all
.Tn NTP
mode 7 packets (i.e. information queries and
1994-09-29 23:04:24 +00:00
configuration requests) from the source. Time service is not affected.
1998-02-19 08:05:46 +00:00
.It nomodify
Ignore all
.Tn NTP
mode 7 packets which attempt to modify the state of the
1994-09-29 23:04:24 +00:00
server (i.e. run time reconfiguration). Queries which return information
1993-12-21 18:36:48 +00:00
are permitted.
1998-02-19 08:05:46 +00:00
.It notrap
1994-04-03 19:50:51 +00:00
Decline to provide mode 6 control message trap service to matching
1994-09-29 23:04:24 +00:00
hosts. The trap service is a subsystem of the mode 6 control message
1994-04-03 19:50:51 +00:00
protocol which is intended for use by remote event logging programs.
1998-02-19 08:05:46 +00:00
.It lowpriotrap
1994-09-29 23:04:24 +00:00
Declare traps set by matching hosts to be low priority. The number of
traps a server can maintain is limited (the current limit is 3). Traps
are usually assigned on a first come, first served basis, with later
trap requestors being denied service. This flag modifies the assignment
algorithm by allowing low priority traps to be overridden by later
requests for normal priority traps.
1998-02-19 08:05:46 +00:00
.It noserve
Ignore
.Tn NTP
packets whose mode is other than 7. In effect, time service
1994-09-29 23:04:24 +00:00
is denied, though queries may still be permitted.
1998-02-19 08:05:46 +00:00
.It nopeer
1994-09-29 23:04:24 +00:00
Provide stateless time service to polling hosts, but do not allocate
peer memory resources to these hosts even if they otherwise might be
considered useful as future synchronization partners.
1998-02-19 08:05:46 +00:00
.It notrust
1993-12-21 18:36:48 +00:00
Treat these hosts normally in other respects, but never use them as
synchronization sources.
1998-02-19 08:05:46 +00:00
.It limited
1994-09-29 23:04:24 +00:00
These hosts are subject to limitation of number of clients from the same
net. Net in this context refers to the IP notion of net (class A, class
1998-02-19 08:05:46 +00:00
B, class C, etc.). Only the first
.Qq client_limit
hosts that have
1994-09-29 23:04:24 +00:00
shown up at the server and that have been active during the last
1998-02-19 08:05:46 +00:00
.Qq client_limit_period
seconds are accepted. Requests from other
1994-09-29 23:04:24 +00:00
clients from the same net are rejected. Only time request packets are
1998-02-19 08:05:46 +00:00
taken into account.
.Qq Private ,
.Qq control ,
and
.Qq broadcast
packets are not subject to client limitation and
1994-09-29 23:04:24 +00:00
therefore are not contributing to client count. History of clients is
kept using the monitoring capability of
1998-02-19 08:05:46 +00:00
.Xr xntpd 8 .
1994-09-29 23:04:24 +00:00
Thus, monitoring is active as long as there is a restriction entry with
1998-02-19 08:05:46 +00:00
the
.Ar limited
flag. The default value for
.Qq client_limit
is 3. The default value for
.Qq client_limit_period
is 3600
1994-09-29 23:04:24 +00:00
seconds. Currently both variables are not runtime configurable.
1998-02-19 08:05:46 +00:00
.It ntpport
1993-12-21 18:36:48 +00:00
This is actually a match algorithm modifier, rather than a restriction
1994-09-29 23:04:24 +00:00
flag. Its presence causes the restriction entry to be matched only if
1998-02-19 08:05:46 +00:00
the source port in the packet is the standard
.Tn NTP
UDP port (123). Both
.Em ntpport
and
.Pf non\- Em ntpport
may be specified. The
.Em ntpport
is considered more specific and is sorted later in the list.
.El
.It Xo unrestrict
.Ar address
.Ar mask
.Ar flag
.Op Ar flag
.Xc
1993-12-21 18:36:48 +00:00
Remove the specified flag(s) from the restrict list entry indicated
by the
1998-02-19 08:05:46 +00:00
.Ar address
1993-12-21 18:36:48 +00:00
and
1998-02-19 08:05:46 +00:00
.Ar mask
1993-12-21 18:36:48 +00:00
arguments.
1998-02-19 08:05:46 +00:00
.It Xo delrestrict
.Ar address
.Ar mask
.Op Ar ntpport
.Xc
1993-12-21 18:36:48 +00:00
Delete the matching entry from the restrict list.
1998-02-19 08:05:46 +00:00
.It monitor Ar yes|no
1994-09-29 23:04:24 +00:00
Enable or disable the monitoring facility. Note that a
1998-02-19 08:05:46 +00:00
.Em monitor Ar no
1993-12-21 18:36:48 +00:00
command followed by a
1998-02-19 08:05:46 +00:00
.Em monitor Ar yes
1993-12-21 18:36:48 +00:00
command is a good way of resetting the packet counts.
1998-02-19 08:05:46 +00:00
.It readkeys
Cause the current set of authentication keys to be purged and a new set
1994-09-29 23:04:24 +00:00
to be obtained by rereading the keys file (which must have been
specified in the
1998-02-19 08:05:46 +00:00
.Nm xntpd
1994-09-29 23:04:24 +00:00
configuration file). This allows encryption keys to be changed without
1993-12-21 18:36:48 +00:00
restarting the server.
1998-02-19 08:05:46 +00:00
.It Xo trustkey
.Ar keyid
.Op Ar keyid
.Op Ar keyid
.Op Ar keyid
.Xc
Add one or more keys to the trusted key list. When authentication is
1994-09-29 23:04:24 +00:00
enabled, peers whose time is to be trusted must be authenticated using a
trusted key.
1998-02-19 08:05:46 +00:00
.It Xo untrustkey
.Ar keyid
.Op Ar keyid
.Op Ar keyid
.Op Ar keyid
.Xc
Remove one or more keys from the trusted key list.
.It authinfo
Return information concerning the authentication module, including
1993-12-21 18:36:48 +00:00
known keys and counts of encryptions and decryptions which have been
done.
1998-02-19 08:05:46 +00:00
.It setprecision Ar precision_value
Set the precision which the server advertises to the specified value.
1994-09-29 23:04:24 +00:00
This should be a negative integer in the range -4 through -20.
1998-02-19 08:05:46 +00:00
.It traps
1994-09-29 23:04:24 +00:00
Display the traps set in the server. See the source listing for further
information.
1998-02-19 08:05:46 +00:00
.It Xo addtrap
.Ar address
.Op Ar port
.Op Ar interface
.Xc
1994-09-29 23:04:24 +00:00
Set a trap for asynchronous messages. See the source listing for further
information.
1998-02-19 08:05:46 +00:00
.It Xo clrtrap
.Ar address
.Op Ar port
.Op Ar interface
.Xc
1994-09-29 23:04:24 +00:00
Clear a trap for asynchronous messages. See the source listing for
further information.
1998-02-19 08:05:46 +00:00
.It reset Ar ...
1994-09-29 23:04:24 +00:00
Clear the statistics counters in various modules of the server. See the
source listing for further information.
1998-02-19 08:05:46 +00:00
.El
.Sh SEE ALSO
.Xr xntpd 8
.Sh HISTORY
Written by
.An Dennis Ferguson
at the University of Toronto.
.Sh BUGS
.Nm Xntpdc
1994-09-29 23:04:24 +00:00
is a crude hack. Much of the information it shows is deadly boring and
could only be loved by its implementer. The program was designed so that
new (and temporary) features were easy to hack in, at great expense to
the program's ease of use. Despite this, the program is occasionally
useful.