From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] Snapshot `0.0.20161223` Available
Date: Fri, 23 Dec 2016 21:22:54 +0100 [thread overview]
Message-ID: <CAHmME9r6N3s=GtAzV5gWDH-HjTvU2mjCrEyZxBxJ_RDX_PvWhw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4AvTav-6Wt40ghvSX22VdE0icTMHhWyKQnOBHLdRt2DA@mail.gmail.com>
On Fri, Dec 23, 2016 at 9:19 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I still don't understand what the change to AI_ADDRCONFIG means/does.
>
> Are you saying fe80:: addresses are useful?
This is just on the tools. Sometimes people like to specify IP
addresses in their config files for endpoints of peers:
[Peer]
PublicKey=ABCDE
Endpoint=[2607:5300:61:14f::c05f:543]:24444
And then they like to call `wg setconf` early on in their init scripts
to parse the config file and setup the interface.
I pass all endpoints to getaddrinfo, regardless of whether or not its
an IP or a hostname, since getaddrinfo is good at deciding what's what
and what to do. The problem before was that getaddrinfo would refuse
to parse v6 addresses if there wasn't an interface with a v6 address.
Removing AI_ADDRCONFIG fixes that.
https://git.zx2c4.com/WireGuard/commit/?id=bfe364e18364cdd9a1cb6fa545a3240c93a33c83
next prev parent reply other threads:[~2016-12-23 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 20:15 Jason A. Donenfeld
2016-12-23 20:19 ` Dave Taht
2016-12-23 20:22 ` Jason A. Donenfeld [this message]
2016-12-25 22:42 ` Introduction of XChaCha20Poly1305 (Was: [ANNOUNCE] Snapshot `0.0.20161223` Available) Baptiste Jonglez
2016-12-25 22:55 ` Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHmME9r6N3s=GtAzV5gWDH-HjTvU2mjCrEyZxBxJ_RDX_PvWhw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=dave.taht@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).