[ntp:questions] (Software) timeserver for windows being broadcast-able incl. keys

Danny Mayer mayer at ntp.isc.org
Sat Mar 17 15:18:21 UTC 2007


Per Hedeland wrote:
> In article <45FAAA30.2080401 at cag.zko.hp.com> Tom Smith
> <smith at cag.zko.hp.com> writes:
>> Erik wrote:
>>> On 15 mrt, 17:21, Tom Smith <s... at cag.zko.hp.com> wrote:
>>>>> broadcast 145.47.51.127 key 1
>>>>> broadcast 145.47.51.255 key 1
>>>>> broadcast 145.47.52.127 key 1
>>>>> broadcast 145.47.53.127 key 1
>>>> That's the right idea, but the second one above already
>>>> includes the first.
> 
> How do you figure that? If (according to latest report) there are two
> networks a) 145.47.51.0/25 and b) 145.47.51.128/25, the address
> 145.47.51.255 doesn't "include" 145.47.51.127 in any way. 145.47.51.127
> is the broadcast address for a), 145.47.51.255 is the broadcast address
> for b) - and hosts on network a) will not see 145.47.51.255 as a
> broadcast address - in fact they will just see it as a random address on
> a remote network. A broadcast address is either 255.255.255.255 or one
> where the network part matches exactly and the host part is all-ones.
> 

There's currently a problem with the broadcast address 255.255.255.255
(see bug #779 https://ntp.isc.org/bugs/show_bug.cgi?id=779) so don't use it.

Danny




More information about the questions mailing list