Yo Eric! On Tue, 5 Jun 2018 05:20:56 -0400 "Eric S. Raymond via devel" <devel@ntpsec.org> wrote:
> Matthew Selsky <matthew.sel...@twosigma.com>:
> > interface listen 127.0.0.1
> > interface listen ::1
> > interface listen address
Oh, I'm starting to see the confusion. The terminology in ntp.conf
is just wrong. I should have checking the ntp.conf man page before
commenting.
An 'interface' is like: eth0, lo, enp3s0, wlp2s0, enp4s0u2u4.
But in the case of ntp.conf, the 'interface' is taking IPv4 addresses,
IPv6 addresses, and hostnames. So the ntp.conf 'interface' has nothing
at all like an interface. It is an address.
There may be perfectly sound reasons to specify an interface, but the
ntp.conf keyword interface does nothing of the sort. It specifies
an address, not an interface.
Thus my confusion. At a minimum the terminology needs to be fixed.
I would suggest 'bind' as a much better keyword. MySQL, SSH, Apache, etc.
all "bind to an address". Although some daemons support both:
bind-interface, and bind-address. better yet, ntp.conf 'interface'
should be chnaged to bind-address.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpXYLf1H4Zjv.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
