All,
How do you set a Solaris 9 server which received ntp updates from a ntp server to broadcast them on a local subnet. I have created a /etc/inet/ntp.conf file to receive the updates from a server on network and need to make this server become like a ntp relay from the main server.
Any... (1 Reply)
Hi folks,
The server time is no tgetiing synched up with the NTP server.
I tried ntpdate -u <ipadress> this is not working. please help out.
regards,
Sag. (7 Replies)
Hello all,
What would be the most convienint and proper way on syncing up the time and date on Solaris 8 servers with an NTP server?
Any help would be appreciated. Thanks (2 Replies)
All,
I need to write a script which can determine if my NTP client is X second off from the NTPD server time. I am looking for a crafty oneliner to calculate the time difference? (3 Replies)
I need to configure an NTP daemon on a "bridge-PC" connected on 2 LANs. It is expected to read the correct time on a time server on the first LAN and behave as a server for the second LAN.
Can I do both the things with ntpd?
In other words, is ntpd able to work as client and server at the same... (3 Replies)
All here, thank you for listening. Now I've set up a Linux NTP server by adding a external windows NTP server in /etc/ntp.conf. Then I start the ntpd daemon. But how often does the Linux NTP server update its time with the external NTP server? I've looked up everywhere but found no information... (1 Reply)
Hi
I am looking to have an NTP server that will support both ipv4 and ipv6 clients. Is there anything specific about the configuration that I should be looking at? (7 Replies)
Hi folks, I have developed a Linux server for my customer. After migrating the server to my customer site, I was trying to sync its time to the NTP time servers at my customer site.
Below is the ntp.conf:
% vi /etc/ntp.conf
# Permit time synchronization with our time source, but do not
# permit... (2 Replies)
We had a network problem a couple of days before that caused 1 interface to down and up. But today I have noticed that our date is wrong, our system have 4 servers and the other 3 are OK.
I used <date> command, the result is: Fri Jan 2 17:57:55 ICT 1970
I have tried set date to be the same as... (3 Replies)
Discussion started by: salvation3103
3 Replies
LEARN ABOUT OSF1
ntp.keys
ntp.keys(4) Kernel Interfaces Manual ntp.keys(4)NAME
ntp.keys - Network Time Protocol (NTP) authentication key file
DESCRIPTION
The NTP standard specifies an extension to allow verification of the authenticity of received NTP packets and to provide an indication of
authenticity in outgoing packets. This is implemented in xntpd using the MD5 algorithm to compute the message-digest. The specification
allows any one of possibly 4 billion keys, numbered with 32-bit key identifiers, to be used to authenticate an association. The servers
involved in an association must agree on the key and key identifier used to authenticate their data, though they must each learn the key
and key identifier independently. In MD5, the keys are 64 bits (8 bytes). The xntpd daemon reads its keys from a file specified using the
-k command line option, or the keys statement in the configuration file. While key number 0 is fixed by the NTP standard (as 56 zero bits)
and may not be changed, one or more of the keys numbered 1 through 15 may be arbitrarily set in the keys file.
One of the keys may be chosen, by way of the configuration file requestkey statement, to authenticate run time configuration requests made
using the xntpdc(8) program. The latter program obtains the key from the terminal as a password, so it is generally appropriate to specify
the key chosen to be used for this purpose in ASCII format.
The NTP key file uses the same comment conventions as the configuration file. Key entries use a fixed format of the form: keyno type key
In this format: Is a positive integer. Is a single character that defines the format the key is given in. This is always M, representing
Message Digest (MD5) on Tru64 UNIX systems. Is the key itself. The MD5 algorithm key is a 1-to-8 character ASCII string. Because of the
simple tokenizing routine, you cannot use the following characters in an ASCII key: " " (space), "#" (number sign), "", "0, and " ". Note
that both the keys and the authentication scheme (MD5) must be identical between a set of peers sharing the same key number.
EXAMPLES
The following sample key file shows two defined NTP keys: 2 M RIrop8KPPvQvYotM # MD5 key as a random ASCII string 14 M sundial
# MD5 key as an ASCII string
FILES
Conventional name of the key file
RELATED INFORMATION
Commands: ntpdate(8), ntpq(8), xntpd(8), xntpdc(8)
Files: ntp.conf(4)
Network Administration delim off
ntp.keys(4)