[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/23705 (ntpd can not be restricted to certain interfaces)
The following reply was made to PR bin/23705; it has been noted by GNATS.
From: Frank Kardel <kardel%acrys.com@localhost>
Subject: Re: bin/23705 (ntpd can not be restricted to certain interfaces)
Date: Sun, 22 Nov 2009 21:58:23 +0100
The bug discussion should go to the NTP specific forums (c.p.t.ntp and
the mailing lists (see http://support.ntp.org).
E. g. for autokey a knowledge of the local address a packet was sent to
is necessary and binding to specific ports
is one of the more portable ways to find out about on which
address/interface a packet was received. On these lists are long
discussions of this topic.
The topic is not too simple to discuss. As I said the next real release
will have mechanisms to refrain from binding
to certain interfaces/addresses.
If we had a perfect world API-wise across all operating systems ntpd is
running on things would be much simpler....
Jukka Ruohonen wrote:
> The following reply was made to PR bin/23705; it has been noted by GNATS.
> I think this should remain open as the issue of binding to all interfaces is
> still a bug, regardless of the access control based on interfaces. Imagine
> for instance running ntpd(8) on a 24-port switch, which will waste at least
> 48 file descriptors.
Main Index |
Thread Index |