NTS update

[Hal Murray]

>> I have 1.1.0j (Debian) talking to 1.0.2o (FreeBSD)
>> Works.
> And vice-versa?

Yes.

--------

>> 2. A way to see both the NTS name/IP and matching NTPD name/IP

2019-03-22T12:55:52 ntpd[10362]: NTSc: nts_probe connecting to 
pi3.rellim.com:123 => [2001:470:e815::23]:123

Is that enough?  (client side)

There is a bug on the server side with the IPv6 printout.  I'm working on it, 
but no luck so far.  But that line has IP Address and port number.  No names 
needed on the server side.


> 2019-03-22T12:55:52 ntpd[10362]: NTSc: Got 8 cookies, length 104, aead=15.
> 2019-03-22T12:55:52 ntpd[10362]: NTSc: NTS-KE req to pi3.rellim.com took 0.028 sec, OK
> 2019-03-22T12:55:52 ntpd[10362]: DNS: dns_check: processing pi3.rellim.com, 1, 21801
> 2019-03-22T12:55:52 ntpd[10362]: DNS: Server skipping: 2001:470:e815::23 

That "skipping" line is important.  It's trying to add the IP address to the 
peer struct for a server but some (other?) peer already exists with that 
address.

Is that the first try or a retry?  If it's a retry, what happened on the 
first.  If it's the first, do you have another non-NTS server for that host?





-- 
These are my opinions.  I hate spam.