[ntp:hackers] Re: Manycast interfering with client packets?
mayer at ntp.isc.org
Fri Apr 21 19:46:06 UTC 2006
The problem is that the client isn't sending in more than one mode, in
this case it's just sending a client packet (mode 3). The server is set
up as a multicast server, but upon receipt of the mode 3 packet it sees
that it is set up as a multicast server and drops the packet. Use deacon
as a multicast server and set up another system just as a simple client.
You will see that deacon will drop the packet asserting that it is a
manycast server which it was not set up to do.
Multicast does not mean that all clients need to be multicast clients.
David L. Mills wrote:
> Works for me. I set deacon as a mulitcast server and howland as a
> broadcast server and whimsy enabled for both multicast and broadcast
> client. The association matching rules and crypto gear go nuts if the
> same server sends packets in different modes to the same client.
More information about the hackers