About:
OpenNTPd is a portable implementation of the Network Time Protocol. It provides the ability to sync the local clock to remote NTP servers and can act as an NTP server itself, redistributing the local clock.

Author:
OpenBSD team <bugs (at) openbsd (dot) org> [contact developer]

Rating:	reset 1 2 3 4 5 6 7 8 9 10
8.50/10.00 (2 votes)

Homepage:
http://www.openntpd.org/
Tar/GZ:
ftp://ftp.openbsd.org/[..]b/OpenBSD/OpenNTPD/openntpd-3.9p1.tar.gz
Changelog:
ftp://ftp.openbsd.org/pub/OpenBSD/OpenNTPD/ChangeLog
BSD Ports URL:
http://openntpd.org/ftp.html
Mirror site:
http://openntpd.org/portable.html

Trove categories: [change]

[Development Status]		4 - Beta, 6 - Mature
[License]		OSI Approved :: BSD License (original)
[Operating System]		POSIX
[Topic]		System :: Networking

Dependencies: [change]
OpenSSL (optional)
Pseudo Random Number Generator Daemon (optional)
[download links]

 Branches

Branch	Version	Last release	License	URLs
Stable	3.9p1	17-May-2006	BSD License (original)
Development	20050127	05-Jun-2005	BSD License (original)

 Comments

[»] Openntpd Server mode
by broccoli - Jan 22nd 2005 02:38:21

I really hate the ntp.org reference implementation..

I was glad to see openntpd, but i looks like i'm to stupid to configure the ntpd:

I set 'listen on $external_ip' in ntpd.conf. It binds to port 123 (netstat -lnp & lsof) but it does not reply to requests sent by other servers, even 'nmap -sU -p 123' fails.

(and ntpd --help segfaults on solaris ;-) )

Hmm?

[reply] [top]

[»] Re: Openntpd Server mode
by Darren Tucker - Feb 4th 2005 20:47:31


> I set 'listen on $external_ip' in
> ntpd.conf. It binds to port 123 (netstat
> -lnp & lsof) but it does not reply
> to requests sent by other servers, even
> 'nmap -sU -p 123' fails.
>
> (and ntpd --help segfaults on solaris
> ;-) )

Some servers (eg the reference implementation) won't sync to a server that doesn't set the precision field, which openntpd didn't. I don't know why nmap doesn't work, though.

The segfault was my fault, I didn't initialize __progname in the compat library for platforms that don't have a real __progname.

Both of those have been fixed in the snapshots and will be fixed in the next release.

[reply] [top]

---

[»] This is not an NTP daemon
by Jonas Bofjall - Dec 8th 2004 02:04:20

I would like to issue a warning here: It seems like this is does not conform to the full NTP protocol at all and it nothing but a simple SNTP daemon, of which there are many. It is false marketing and the documentation conveniently skips mentioning it. I feel let down by the otherwise so skillful programmers behind this.

After spending a lot of time trying to install and understand this software I suspected this and search the web for references. Turns out Brad Knowles has a few things to say about openntpd.

Be warned that if you use SNTP instead of NTP and the server clock breaks down, all your time will be compromised.

[reply] [top]

[»] Re: This is not an NTP daemon
by Darren Tucker - Dec 12th 2004 05:48:13


> Turns out Brad Knowles has a few things
> to say about openntpd.

Some of the issues raised by Brad have been resolved in the development tree a while ago and are now resolved in 3.6.1p1. Some of the other comments are arguable or misleading.

I have posted a (long) response to most of the issues raised.

[reply] [top]

---