From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Dave Täht" <dave@taht.net>, "Juliusz Chroboczek" <jch@irif.fr>
Subject: [RFC] Multicast and IPv6 Link Local Addresses
Date: Fri, 7 Apr 2017 16:02:49 +0200 [thread overview]
Message-ID: <CAHmME9poZPFbYhitnK8UvDB-32hLRcTFc4vAwaUPwGEz0wY+Yg@mail.gmail.com> (raw)
Hey list,
Various networking people have been poking and prodding about
supporting IPv6 Link Local addresses and about supporting special
multicast addresses. *I MAY VERY WELL NEVER CHOOSE TO IMPLEMENT THIS*
but in case I do, I wanted to start spec'ing out what this might look
like in order to think about it better. There are a lot of odd
concerns to take into account, so I doubt that the below will wind up
as a final solution.
For these two options below, I introduce them with corresponding
configuration nobs. Since I don't really like adding nobs, it's
entirely likely that on the small chance I do wind up implementing
this, it would be without the nobs and just always on.
== Multicast ==
# wg set wg0 multicast on
When multicast mode is turned on, packets sent to the special address
ranges 224.0.0.0/24 or fe02::/16 are sent to every peer on that
interface.
== IPv6 Link Local Addresses ==
# wg set wg0 llv6 on
This command fails and returns -ENOTUNIQ if two existing peers have
the same value of hash(pubkey). When this command succeeds:, the wg0
interface receives an automatically assigned IP address of
fe80::hash(interfacepubkey)/64. Every peer has
fe80::hash(peerpubkey)/128 implicitly added to their allowed-ips. When
adding a new peer, if hash(pubkey) is the same value of an existing
peer, the command fails and returns -ENOTUNIQ.
I'm open to thoughts and suggestions about the above ideas.
Thanks,
Jason
next reply other threads:[~2017-04-07 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 14:02 Jason A. Donenfeld [this message]
2017-04-07 14:31 ` Jason A. Donenfeld
[not found] ` <03B23E99-75C4-4598-AC0A-3C65F346675F@gmail.com>
2017-04-07 20:42 ` Jason A. Donenfeld
2017-04-08 12:43 ` Toke Høiland-Jørgensen
2017-04-08 15:44 ` George Walker
2017-04-08 9:39 ` Dan Lüdtke
2017-04-08 17:15 ` Juliusz Chroboczek
2017-04-08 19:05 ` Juliusz Chroboczek
2017-04-17 14:11 ` Baptiste Jonglez
2017-04-17 16:55 ` Toke Høiland-Jørgensen
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=CAHmME9poZPFbYhitnK8UvDB-32hLRcTFc4vAwaUPwGEz0wY+Yg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=dave@taht.net \
--cc=jch@irif.fr \
--cc=toke@toke.dk \
--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).