EndRun Tempus LX GPS, User Manual

Page: 34 / 116

T e m p u s L X G P S U s e r M a n u a l 22
C H A P T E R T H R E E
23 T e m p u s L X G P S U s e r M a n u a l
S E T T I N G U P N T P C L I E N T S O N U N I X - L I K E P L A T F O R M S
You can verify that authentication is being used by issuing the command
associations
to display the characteristics of the client server associations. In the “auth” column of the display,
you should see “OK” for the row corresponding to the Tempus LX server. If you see “bad”, you
should wait a few minutes to be sure that there is a problem since “bad” is the initial state of this
setting. If the “bad” indication persists then you must check your configuration for errors. Typi-
cally this is due to a typing error in creating the
/etc/ntp.keys
file on the client that causes a mismatch
between the keys being used by the server and client. (If you transfer the file by
ftp
or
scp
, this
shouldn’t be a problem.) It is also possible to have a typing error in the
/etc/ntp.conf
file that causes
the needed key to not be included in the “trustedkey” list.
Broadcast/Multicast NTP
Client Setup
Broadcast/multicast client setup is relatively simple, if:
• You have been able to successfully communicate with the Tempus LX on your network.
• Your Tempus LX has been configured to perform broadcasts or multicasts via the front-panel
keypad or by running the
ntpconfig
shell script. (This is not the factory default configuration, so
be sure to run
ntpconfig
.) If you are going to use MD5 authentication, your Tempus LX must have
been configured to operate with authentication in the broadcast/multicast mode, and you must know
which of the trusted keys it is using for broadcast/multicast operation. The example Tempus LX
configuration shown in Chapter 2 - Configuring the Network Time Protocol will be assumed in the
example configuration commands shown here.
• You have installed NTP on your client computer.
• You have successfully performed the
MD5 Authenticated NTP Client Setup
on your client com-
puter, if you plan to use MD5 authentication.
Configure NTP
You must edit the ntp.conf file which
ntpd
, the NTP daemon, looks for by default in the the /etc
directory. Assuming that your Tempus LX server has been configured to use key 2 for broadcast
authentication as shown in the example in chapter 2, make sure that key 2 is included in the
trust-
edkey
line, and add this line to the end of the
ntp.conf
file:
broadcastclient
If you are not using MD5 authentication, you would add these lines:
disable auth
broadcastclient
If you are using multicast instead of broadcast mode, you would replace the
broadcastclient
keyword with the
multicastclient
keyword. You may remove the line added previously in Basic
NTP Client Setup
:
server 192.168.1.245