Serge, I had proposed to the developer's group to unify the commands, but found a frosty reception. As evident, I don't usually muck around in the I/O code. It might help if you posted a bug report on the issue.
Dave Serge Bets wrote: > Hello Dave, > > On Tuesday, May 6, 2008 at 3:13:05 +0000, David L. Mills wrote: > > >>The manycast server will not respond unless it is synchronized to >>something. I modified that for the same terms as orphan broadcast and >>the players now happily play ball. > > > Excellent! Thank you very much, David, I'll try the next snapshot. > > > BTW, why is manycast only designed to use multicast group addresses, and > not also broadcast addresses? I see the code and the doc both requiring > type m "multicast address (IPv4 class D)" for those commands, but don't > understand why broadcast IP is impossible. Something like: > > | manycastclient 192.168.7.255 key 4 iburst > | manycastserver 192.168.7.255 > > prints to syslog: > > | attempt to configure invalid address 192.168.7.255 > > > Cordialement, Serge. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
