On Fri, Feb 5, 2021, at 4:04 PM Hal Murray via devel
wrote:
> > What were you looking for in the branch?
>
> The code that would get the correct source address on server replies.
>
The short version is I looked and it is not there^d^d^d^d^d anywhere I can
see it.
> I don't even know if it is p
> What were you looking for in the branch?
The code that would get the correct source address on server replies.
I don't even know if it is possible. The current code turns on the right
option and then gets the source address when it reads a packet using recvmsg()
or recvfrom().
Is there a s
On Fri, Feb 5, 2021, at 2:42 AM Hal Murray via devel
wrote:
>
> devel@ntpsec.org said:
> > 1208. I stripped out all handling of the netlink socket and fixed around
> the
> > breaks I found. This would reduce NTPsec w/ NTS and IPv4/6 to 5 sockets.
> They
> > are UDP4, UPD6, TCP4, TCP6, and netlink
devel@ntpsec.org said:
> 1208. I stripped out all handling of the netlink socket and fixed around the
> breaks I found. This would reduce NTPsec w/ NTS and IPv4/6 to 5 sockets. They
> are UDP4, UPD6, TCP4, TCP6, and netlink which only spuriously trigger DNS
> retries.
I scanned the patch file an
