[ntp:questions] pool configuration directive on Windows
mayer at ntp.isc.org
Sun Mar 16 01:26:52 UTC 2008
No I haven't thought about IGMP. NTP is only involved in the sense that
it sends an IGMP message to the router notifying it of it's request to
receive multicast messages with a given IP address. It has no other
interaction with IGMP. It's then the router's responsibility to forward
messages with that IP address to the wire on which the multicast
I do not see how this would affect autokey since autokey is done on a
one-to-one basis by specific (non-multicast) address. The multicast
address is not involved in autokey.
I'm not sure what you mean by an autokey name. It's not even clear to me
how you would ensure uniqueness of the name. I am, however, interested.
David L. Mills wrote:
> Understand. You guys have been wizards with the net interfaces. Real
> magic. I haven't heard anybody comment on IGMP and the need to replicate
> for the DVMRP spanning tree. Is that done by IGMP without NTP being
> involved? If so and multiple endpoints result, Autokey would surely scream.
> You may notice in the fog of war that Autokey names potentially can
> replace the IP addresses. Need to work on that...
> Danny Mayer wrote:
>> David L. Mills wrote:
>>> The specific accusation directed to me personally was about the notrust
>>> bit, which change I described in my previous message. I hadn't noticed
>>> the L option change, which was not by my hand.
>> Well it might well have been me since I have touched that code a number
>> of times. I'm intending to get rid of it as soon as Harlan and I have
>> agreement on the syntax of the changes. This will implement listen-on
>> and query-on directives in the configuration file to allow the admins to
>> have control over exactly what addresses and interfaces to use to
>> receive and transmit NTP packets. I already have working code for this.
>> We just have details to resolve.
> questions mailing list
> questions at lists.ntp.org
More information about the questions