Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Derrick Lyndon Pallas <derrick@pallas.us>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Interest in adding multicast support to Wireguard?
Date: Mon, 21 Sep 2020 00:13:00 -0700	[thread overview]
Message-ID: <9b4ba85a-633a-04ed-ca15-eb29d476cd57@pallas.us> (raw)

I know this has come up a few times before, but if there was resolution, 
I couldn't find it.

I am trying to set up a hub-and-spoke network with many clients 
connected to a single concentrator. One application I need to support 
relies on mDNS. Because Wireguard does not allow overlapping ranges (for 
understandable reasons), this works on point-to-point links with two 
peers but not on hub-and-spoke or other multi-peer setups. This would be 
possible if every peer had its own hub interface, but that seems like an 
inelegant, error-prone workaround.

Some have suggested running vxlan or another encapsulation method on top 
of Wireguard, but that's not possible in this situation because I do not 
control the software running on the peers. Typically, they'll just be 
running the official Wireguard apps for MacOS or Windows.

Hacking Wireguard to understand the multicast range and to 
clone-and-forward this traffic to all peers does work. If there is wider 
interest in that specific feature, I'm happy to work what I have into 
something that could be upstreamed. Currently the range is global and 
hard-coded, but I could imagine wanting fine-grained control over which 
peers were interested in specific multicast addresses, e.g., for a 
user-space daemon managing IGMP subscriptions. However, before I spent 
time on any of the above, I wanted to gauge whether there was interest 
and whether that kind of feature might be accepted at all.

Thanks, ~Derrick



             reply	other threads:[~2020-09-21  7:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  7:13 Derrick Lyndon Pallas [this message]
2020-09-21  9:57 ` Toke Høiland-Jørgensen
2020-09-21 15:16   ` Derrick Lyndon Pallas
2020-09-21 11:17 ` AW: " Florian Werner
2020-09-21 15:16   ` Derrick Lyndon Pallas
2020-09-21 11:24 ` Jason A. Donenfeld
2020-09-21 15:04   ` Reid Rankin
2020-09-21 15:16     ` Derrick Lyndon Pallas
2020-09-22 18:54       ` Derrick Lyndon Pallas
2020-09-22 19:38         ` Reid Rankin
2020-09-22 20:26           ` Derrick Lyndon Pallas
2020-09-21 15:17   ` Derrick Lyndon Pallas
2020-09-27 17:50 ` Derek Fawcus

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=9b4ba85a-633a-04ed-ca15-eb29d476cd57@pallas.us \
    --to=derrick@pallas.us \
    --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).