sockaddr_storage

[Mark Atwood]

I like the idea of removing more IPv4 specific code.

If we do, can we still get arrival timestamp from the kernel?

How do standard display functions display v6 mapped v4 addresses?   How do
we want them displayed?

Are there any places left in the code that are storing addresses in
packed-4-octets or ints?

..m

On Fri, Jan 27, 2017 at 12:16 PM Gary E. Miller <gem at rellim.com> wrote:

> Yo Eric!
>
> On Fri, 27 Jan 2017 15:01:19 -0500
> "Eric S. Raymond" <esr at thyrsus.com> wrote:
>
> > Gary E. Miller <gem at rellim.com>:
> > > Yes, but NTP does not have to.  NTP can just open an IPv6 socket and
> > > shove all IPv6 and IPv4 in through that socket.  Apache does this,
> > > sendmail does this, nginx does this, postfix does this.  Very
> > > standard and very easy.
> >
> > That's interesting.  Does this mean we could throw out all
> > IPV4-specific code and use IPV6 logic everywhere?
>
> Yes.
>
> > I didn't think an IPv6 accept() would take incoming IPv4 connections
>
> Yes.
>
> > - is there a way to make it take both?
>
> It does by default, if you only open an IPv6 socket.
>
> Look at 'man 7 ipv6'
>
> Or here: http://man7.org/linux/man-pages/man7/ipv6.7.html
>
>     "IPv4 connections can be handled with the v6 API by using the
>     v4-mapped-on-v6 address type; thus a program needs to support
>     only this API type to support both protocols.  This is handled
>     transparently by the address handling functions in the C library."
>
>
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>         gem at rellim.com  Tel:+1 541 382 8588 <(541)%20382-8588>
>
>             Veritas liberabit vos. -- Quid est veritas?
>     "If you can’t measure it, you can’t improve it." - Lord Kelvin
> _______________________________________________
> devel mailing list
> devel at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20170127/08a8bc79/attachment.html>