gdt@ir.bbn.com (Greg Troxel) writes:
> This is hard with ntp, since it is not the usual try-to-connect-once
> program.  Arguably an NTP association should have the concept of
> multiple addresses, and it should try them all, finding the best one,
> or something.

Ntp has a couple of errors in that class.  If you have more than one
interface on your host and you select a broadcast/multicast
transmission method ntp doesn't have any provisions for selecting
which interface you want to use.  It simply uses the first one.
Fixing that is trivial, but requires extending the command parser a
bit and touching a bunch of files.  It really needs buy-off from the
ntp folks.

(ob google: As others have pointed out the -4 can be forced from the
command line or from the server/peer line in the ntp.conf file.)

-wolfgang