🚀 go-pugleaf

Now that I finally built the suite on AIX/6000, I'm utterly unable to
get it to synchronize to any servers.

I believe my LAN server is version 2, but I'm not sure.

A simple test:

    % ntpdate -d ntp1.uai.com
    ntpdate: ntpdate version 3.1
    transmit(149.86.1.3)
    transmit(149.86.1.3)
    transmit(149.86.1.3)
    transmit(149.86.1.3)
    transmit(149.86.1.3)
    server 149.86.1.3, port 123
    stratum 0, precision 0, leap 00, trust 000
    refid [0.0.0.0], delay 0.0000, dispersion 64.0000
    transmitted 4, in filter 4
    reference time:      00000000.00000000  Wed, Feb  6 2036 22:28:16.000
    originate timestamp: 00000000.00000000  Wed, Feb  6 2036 22:28:16.000
    transmit timestamp:  af102764.61548000  Tue, Jan 26 1993 13:11:00.380
    filter delay:  0.0000   0.0000   0.0000   0.0000  
                   0.0000   0.0000   0.0000   0.0000  
    filter offset: 0.00000  0.00000  0.00000  0.00000 
                   0.00000  0.00000  0.00000  0.00000 
    delay 0.0000, dispersion 64.0000
    offset 0.0000000

    ntpdate: no server suitable for synchronization found

The server appears to be ignoring me.  Now try version 2:

    % ntpdate -o 2 -d ntp1.uai.com
    ntpdate: ntpdate version 3.1
    transmit(149.86.1.3)
    receive(149.86.1.3)
    transmit(149.86.1.3)
    receive(149.86.1.3)
    transmit(149.86.1.3)
    receive(149.86.1.3)
    transmit(149.86.1.3)
    receive(149.86.1.3)
    transmit(149.86.1.3)
    server 149.86.1.3, port 123
    stratum 0, precision 0, leap 00, trust 000
    refid [0.0.0.0], delay 0.0000, dispersion 64.0000
    transmitted 4, in filter 4
    reference time:      00000000.00000000  Wed, Feb  6 2036 22:28:16.000
    originate timestamp: 00000000.00000000  Wed, Feb  6 2036 22:28:16.000
    transmit timestamp:  af1027d5.51ee3000  Tue, Jan 26 1993 13:12:53.320
    filter delay:  0.0000   0.0000   0.0000   0.0000  
                   0.0000   0.0000   0.0000   0.0000  
    filter offset: 0.00000  0.00000  0.00000  0.00000 
                   0.00000  0.00000  0.00000  0.00000 
    delay 0.0000, dispersion 64.0000
    offset 0.0000000

    ntpdate: no server suitable for synchronization found

Looks like the server is version 2, but something about the returned
information makes ntpdate unhappy.  Perhaps it works as version 1:

    % ntpdate -o 1 -d ntp1.uai.com
    ntpdate: ntpdate version 3.1
    transmit(149.86.1.3)
    receive(149.86.1.3)
    transmit(149.86.1.3)
    receive(149.86.1.3)
    transmit(149.86.1.3)
    receive(149.86.1.3)
    transmit(149.86.1.3)
    receive(149.86.1.3)
    transmit(149.86.1.3)
    server 149.86.1.3, port 123
    stratum 3, precision -6, leap 00, trust 000
    refid [128.145.228.3], delay 0.0476, dispersion 0.0029
    transmitted 4, in filter 4
    reference time:      af102796.7c9e8000  Tue, Jan 26 1993 13:11:50.486
    originate timestamp: af1027c9.288b3000  Tue, Jan 26 1993 13:12:41.158
    transmit timestamp:  af1027f0.b466c000  Tue, Jan 26 1993 13:13:20.704
    filter delay:  0.0491   0.0479   0.0479   0.0476  
                   0.0000   0.0000   0.0000   0.0000  
    filter offset: -39.5461 -39.5443 -39.5519 -39.5495
                   0.00000  0.00000  0.00000  0.00000 
    delay 0.0476, dispersion 0.0029
    offset -39.5494995

    ntpdate: step time server 149.86.1.3 offset -39.5494995

Okay.  Reviewing the posts of the last few months confirms my
impression that there is a problem with using lower-version servers.
Perhaps this is being fixed?  Does this problem affect xntpd too?

I'm not sure I really care about ntpdate, since I'm not planning to
use it in production.  I started using it when I couldn't get the
daemon to do anything with the server.

My configuration:

    server       ntp1 version 2
    #
    keys         /usr/local/etc/xntp.keys
    trustedkey    1
    requestkey   15
    controlkey   16
    driftfile    /usr/local/etc/xntp.drift
    resolver     /usr/local/etc/xntpres
    #
    restrict default notrust nomodify
    restrict 127.0.0.1

First, ntpq:

    % ntpq -c peers
         remote           refid      st when poll reach   delay  offset    disp
    ===========================================================================
     vaxult.uai.com  0.0.0.0         16   64   64    0     0.00    0.00 16000.0

Now, xntpdc:

    % xntpdc -c peers
         remote           local      st poll reach  delay   offset   disp
    ======================================================================
    =vaxult.uai.com  149.86.1.16     16   64    0  0.0000  0.000000 16.000

How long do I have to wait for the daemon to decide whether or not it
will accept the server's idea of time?  I've also tried it configured
as "server ntp1 version 1" with identical results.

Oh Lords of Time, please help me understand how to get this to work.$$