https://bugzilla.novell.com/show_bug.cgi?id=688132 https://bugzilla.novell.com/show_bug.cgi?id=688132#c0 Summary: "rcntp start" hangs 6 minuest when using ipv6 only servers Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: sweet_f_a@gmx.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 Hi, I'm using ntp with ipv6 only, i.e. in /etc/sysconfig/ntp I have NTPD_OPTIONS="-g -u ntp:ntp -6" on all my client and server machines. "rcntp start" tries to set initial time doing sntp -s ntpserver (where ntpserver is the first one it finds in ntp.conf) If ntpserver resolves to both A and AAAA when sntp obviously is using ipv4 first. That means: $ sntp -4 ipv6-only-server timeout, of course $ sntp -6 ipv6-only-server works correctly $ sntp ipv6-only-server timeout, but shouldn't! BTW ntpq and ntpdc are working correctly and using AAAA record first, for example: $ ntpq -p ipv6-only-server correct $ ntpdc -p ipv6-only-server correct Thus this seems to be a bug in upstream. One could say that if my ntpserver dns record resolves A and AAAA record, then it should listen to both ipv4 and ipv6 but it's still a bug in sntp and its not nice to specify NTPD_OPTIONS="-6" and then using ipv4 nevertheless and moreover as the first choice. BTW rcntp script has another bug: If I explicitly specify all my ntp servers in ntp.conf as ipv6 ones that way: server -6 server1 server -6 server2 .. then "rcntp ntptimeset" doesn't find any server for initialization: $ rcntp start Time could not be synchronized Starting network time protocol daemon (NTPD) cu, Rudi Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.