From: Arti Zirk <arti.zirk@gmail.com>
To: Reid Rankin <reidrankin@gmail.com>, wireguard@lists.zx2c4.com
Subject: Re: Thoughts on wg-dynamic
Date: Mon, 06 Apr 2020 11:28:33 +0300 [thread overview]
Message-ID: <c41fb7b6ba61a41804ef50a7c92857367c51a36e.camel@gmail.com> (raw)
In-Reply-To: <CAMaqUZ2i+LFg8wreOr=H1gB5ocw9+N5uacsZukcjEx6xNrbdkQ@mail.gmail.com>
On P, 2020-04-05 at 19:43 -0400, Reid Rankin wrote:
> However, I've taken it one step further, by using
> cryptographically-generated addresses; each peer automatically gets
> fe80:(truncated hash of pubkey)/128 stuck in its allowed IP list.
> (I'm considering harmonizing this address generation algorithm with
> RFC3972 in the future.) This means that initiating the protocol
> requires no configuration other than the public key of the peer you'd
> like to contact.
While back there was a tool posted to this mailing list[0] that
generated WireGuard IP aadresses from the public key called wg-ip[1].
It would simplify things if that or some other link-local IP genration
algorithm would get integrated into wg-quick toolset.
I have also written a Python version of wg-ip generation algorithm that
might me slightly easier to read[2].
[0] https://lists.zx2c4.com/pipermail/wireguard/2018-April/002593.html
[1] https://github.com/chmduquesne/wg-ip
[2] https://gist.github.com/artizirk/c91e4f8c237dec07e3ad1b286f1855a7
next prev parent reply other threads:[~2020-04-06 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 23:43 Reid Rankin
2020-04-06 8:28 ` Arti Zirk [this message]
2020-04-06 9:46 ` Reid Rankin
[not found] ` <CAFX-c4sfzqEwCk+1Ec7dRtVD60jougU1w9=V-cAQ-8Qk0S+HZg@mail.gmail.com>
2020-04-06 9:46 ` Reid Rankin
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=c41fb7b6ba61a41804ef50a7c92857367c51a36e.camel@gmail.com \
--to=arti.zirk@gmail.com \
--cc=reidrankin@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).