Comments for OpenNTPd
22 Jan 2005 02:38
Openntpd Server mode
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?
12 Dec 2004 05:48
Re: This is not an NTP daemon
> 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 (advogato.org/person/dt...) to most of the issues raised.
08 Dec 2004 02:04
This is not an NTP daemon
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 (bradknowles.typepad.co...) 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.
Re: Openntpd Server mode
> 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 (www.zip.com.au/~dtucke...)
and will be fixed in the next release.