All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Multicast over a wireguard link?
Date: Tue, 20 Dec 2016 19:19:03 +0100	[thread overview]
Message-ID: <8737hiqx9k.fsf@toke.dk> (raw)
In-Reply-To: <CAHmME9o-0qccmg2zbM62fhi_KuEjtDoXZfBFPtf3yyhUKwtfiA@mail.gmail.com> (Jason A. Donenfeld's message of "Tue, 20 Dec 2016 17:29:24 +0100")

"Jason A. Donenfeld" <Jason@zx2c4.com> writes:

> Hi Toke,
>
> Right now, no, there's no multicast. But it wouldn't be that hard to
> add the ability to add the same allowed-ips entry to multiple peers,
> and have WireGuard duplicate the message to all of them.

The multicast destination address is known, so that should work. Would
also serve as a kind of ACL, I guess.

> It's not complicated in theory, but I wonder if this would be
> genuinely useful, and whether or not it'd open up a wormhole of
> potential issues.

Well, I would certainly limit it to multicast addresses. But other than
that it sounds like an excellent idea.

Can wireguard handle routed traffic to an endpoint. I.e. if endpoint A
has address 10.0.0.1/32 and endpoint B has a route 'ip route add
10.10.10.1/24 via 10.0.0.1 dev wg0', would the traffic go where it's
supposed to?

-Toke

  reply	other threads:[~2016-12-20 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 14:53 Multicast over a wireguard link? 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2016-12-20 18:43 Jason A. Donenfeld
2016-12-20 18: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=8737hiqx9k.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=Jason@zx2c4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.