I'm not sure I agree with that behavior (from a client/peer use-case perspective). Wouldn't it make more sense to only use the stack that's actually available? That's how it works with DNS typically: If ghostbyname yields an A and AAAA record, applications don't attempt to use the AAAA record if there is no ipv6 stack configured, right?
Dan Dan Geist dan(@)polter.net ----- Original Message ----- From: "lst hoe02" <[email protected]> To: [email protected] Sent: Friday, November 6, 2015 8:13:10 AM Subject: Re: [Pool] pool IPv4/IPv6 behavior with ntpd Zitat von Dan Geist <[email protected]>: > Hi, all. I noticed this morning that one of my ipv4-only hosts (i.e. > v6 is disabled via sysctl on boot) is pulling in the full list of > all hosts in my internal ntp pool (several A as well as several > AAAA). Obviously, the v6 time sources are never going to be > reachable by a single-stack v4 host. Is this intentional behavior, > or do I need to dig into the code to figure out why it's adding v6 > sources to the list without an active v6 network stack? > You should use the "-4" startoption for ntpd in this case, most programs only check if the kernel is IPv6 capable and not if it is activated configured. Regards Andreas _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
