From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Multicast over a wireguard link?
Date: Tue, 20 Dec 2016 19:43:15 +0100 [thread overview]
Message-ID: <CAHmME9oOJozBq-+UbYiZzF9uBpjMQ=saNPOeXnb2mPYNiKs0iw@mail.gmail.com> (raw)
On Tue, Dec 20, 2016 at 7:40 PM, Toke H=C3=B8iland-J=C3=B8rgensen <toke@tok=
e.dk> wrote:
> Right, but that means that even if multicast is added, a routing
> protocol won't be terribly useful, since it can't tell wireguard which
> subnets lives behind which peers. What I would need is to be able to
> assign /32s (or IPv6 lladdrs) to the interface for each peer, and have
> the kernel routing table determine which subnets should go to each of
> those. My hope was that wireguard could then figure out where to send
> the packet from the /32s (which would be in the wireguard config,
> presumably).
Ahh, I see. In this case, the routing protocol needs to update
WireGuard, not the kernel's routing table. This forces you to
re-envision your routing protocol in terms of "which public key should
get which routes?" which strikes me as an authenticity improvement.
next reply other threads:[~2016-12-20 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 18:43 Jason A. Donenfeld [this message]
2016-12-20 18:55 ` Toke Høiland-Jørgensen
-- strict thread matches above, loose matches on Subject: below --
2016-12-20 14:53 Toke Høiland-Jørgensen
2016-12-20 16:04 ` Dan Lüdtke
2016-12-20 16:29 ` Jason A. Donenfeld
2016-12-20 18:19 ` Toke Høiland-Jørgensen
2016-12-20 18:22 ` Jason A. Donenfeld
2016-12-20 18:40 ` Toke Høiland-Jørgensen
2016-12-21 17:32 ` Jörg Thalheim
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='CAHmME9oOJozBq-+UbYiZzF9uBpjMQ=saNPOeXnb2mPYNiKs0iw@mail.gmail.com' \
--to=jason@zx2c4.com \
--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).