NTS-6001 WEB CONFIGURATION
www.
galsys
.co.uk
galleonsupport
.com
TEL:
+44 (0) 121 608 4433
FAX:
+44 (0) 121 608 4477
AUXILIARY COMMANDS
broadcastclient [novolley]
-
This command enables reception of broadcast server messages to any local interface (type
b) address. Ordinarily, upon receiving a message for the first time, the broadcast client
measures the nominal server propagation delay using a brief client/server exchange with the
server, after which it continues in listen-only mode.
If the novolley keyword is present, the exchange is not used and the value specified in the
broadcastdelay command is used or, if the broadcastdelay command is not used, the default 4.0 ms.
Note that, in order to avoid accidental or malicious disruption in this mode, both the server and
client should operate using symmetric key or public key authentication as described in the
Authentication Options page. Note that the novolley keyword is incompatible with public key
authentication.
manycastserver address [...]
-
This command enables reception of manycast client messages to the multicast group
address(es) (type m) specified. At least one address is required. The NTP multicast address
224.0.1.1 assigned by the IANA should NOT be used, unless specific means are taken to limit
the span of the reply and avoid a possibly massive implosion at the original sender.
Note that, in order to avoid accidental or malicious disruption in this mode, both the server and
client should operate using symmetric key or public key authentication as described in the
Authentication Options page.
multicastclient address [...]
-
This command enables reception of multicast server messages to the multicast group
address(es) (type m) specified.
Upon receiving a message for the first time, the multicast client measures the nominal server
propagation delay using a brief client/server exchange with the server, then enters the broadcast
client mode, in which it synchronises to succeeding multicast messages.
Note that, in order to avoid accidental or malicious disruption in this mode, both the server and
client should operate using symmetric key or public key authentication as described in the
Authentication Options page.
