> I'm even happier if waf autodetects too old openssl. We can't just support
> the latest/coolest/shiniest
It works with all the old systems I have access to. That includes some that
are older than yours. (where age == version number rather than calendar)
I don't have access to Solaris or
Yo Matthew!
On Sat, 23 Mar 2019 02:25:02 +
Matthew Selsky wrote:
> In ntpd/wscript, try replacing this:
>
> use="libntpd_obj ntp M parse RT CAP SECCOMP PTHREAD NTPD "
> "SSL CRYPTO DNS_SD %s SOCKET NSL SCF" % use_refclock,
>
> With:
>
> use="M SSL CRYPTO DNS_SD
On Fri, Mar 22, 2019 at 06:32:10PM -0700, Gary E. Miller via devel wrote:
> I think this is what you want:
Perfect.
> I tried to modify the wscript to do that, but failed...
In ntpd/wscript, try replacing this:
use="libntpd_obj ntp M parse RT CAP SECCOMP PTHREAD NTPD "
"SSL
Yo Matthew!
On Sat, 23 Mar 2019 01:08:06 +
Matthew Selsky wrote:
> This sounds like:
> https://ubuntuforums.org/archive/index.php/t-985136.html
Sure does.
> "The solution is simple, for some reason, when linking the library,
> -lssl must be in front of -lcrypto."
Fingers crossed.
> Can y
On Fri, Mar 22, 2019 at 04:52:33PM -0700, Gary E. Miller via devel wrote:
> Yo Hal!
>
> New issue. I have a really old server that has been running NTPsec
> git head until recently. Now it fails, the openssl is too old.
>
> # openssl version
> OpenSSL 1.0.2o 27 Mar 2018
>
> I know I can updat
Yo Hal!
New issue. I have a really old server that has been running NTPsec
git head until recently. Now it fails, the openssl is too old.
# openssl version
OpenSSL 1.0.2o 27 Mar 2018
I know I can update the openssl, but many people will not be able to...
How do I disable building with openss
Yo Mike!
On Fri, 22 Mar 2019 22:16:43 +
Mike Simpson via devel wrote:
>
> My server khronos.mikieboy.net is also publicly available and running
> current
Cool, I can connect just fine.
> so could be added for the hackathon.
You'll have to context them directly:
NTP WG
"Dieter
> On 22 Mar 2019, at 22:07, Gary E. Miller via devel wrote:
>
> Yo Hal!
>
> On Fri, 22 Mar 2019 14:14:19 -0700
> Hal Murray via devel wrote:
>
> 2019-03-22T12:55:52 ntpd[10362]: DNS: Server skipping:
> 2001:470:e815::23
>>
>>> Looking at this again, when kong connects to pi3, there
Yo Hal!
On Fri, 22 Mar 2019 14:14:19 -0700
Hal Murray via devel wrote:
> > > > 2019-03-22T12:55:52 ntpd[10362]: DNS: Server skipping:
> > > > 2001:470:e815::23
>
> > Looking at this again, when kong connects to pi3, there is no
> > duplicate connection.
>
> Then where did that skipping com
> > > 2019-03-22T12:55:52 ntpd[10362]: DNS: Server skipping:
> > > 2001:470:e815::23
> Looking at this again, when kong connects to pi3, there is no duplicate
> connection.
Then where did that skipping come from? Either there is some other server
slot that has that IP Address, or the NTS path
> Uh, oh. You mean I can't have both an NTS and a non-NTS connection to the
> same address? I want that to compare latency and jitter. That needs a very
> clear error message.
Nope. It might be possible to change, but I doubt if it's worth the effort.
You can compare -4 with -6.
I've adde
Yo Hal!
> > > 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
Yo Hal!
On Fri, 22 Mar 2019 13:30:48 -0700
Hal Murray via devel wrote:
> >> 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)
I
>> 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? (clie
Yo Hal!
On Thu, 21 Mar 2019 21:49:31 -0700
Hal Murray via devel wrote:
> > What's your environment? I'm passing "ntp" to getaddrinfo.
> > Ah, that's the bug. Don't do that. There is no offical tcp/ntp
> > port assigned. So trying to look it up is not going to work
> > well...
>
> For "n
Yo Hal!
On Fri, 22 Mar 2019 01:19:23 -0700
Hal Murray via devel wrote:
> >>> Gentoo unstable is on 1.1.0j. Stable is on 1.0.2r. =20
> >> I'd expect that case to work.
> > Me too.
>
> I have 1.1.0j (Debian) talking to 1.0.2o (FreeBSD)
> Works.
And vice-versa?
> >> Do you get an intere
Yo Hal!
On Fri, 22 Mar 2019 01:22:37 -0700
Hal Murray via devel wrote:
> > I don't care if it is ntpq, ntpmon, log files, whatever. Right now
> > I don't know how to get the info any way.
>
> I still don't know what you want.
As I said before:
> > 2. A way to see both the NTS name/IP and
> I don't care if it is ntpq, ntpmon, log files, whatever. Right now I don't
> know how to get the info any way.
I still don't know what you want.
I've tried hard to make sure that everything interesting is in the log files
while at the same time not making things too verbose. Please look c
>>> Gentoo unstable is on 1.1.0j. Stable is on 1.0.2r. =20
>> I'd expect that case to work.
> Me too.
I have 1.1.0j (Debian) talking to 1.0.2o (FreeBSD)
Works.
>> Do you get an interesting error message?
>Nope. The client gets the 8 cookies, but the NTPD fails, silently.
Does the 8 count dow
19 matches
Mail list logo