From: Derrick Lyndon Pallas <derrick@pallas.us>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Interest in adding multicast support to Wireguard?
Date: Mon, 21 Sep 2020 08:17:37 -0700 [thread overview]
Message-ID: <e5031f21-01ee-d3f1-fc27-4140fc1da363@pallas.us> (raw)
In-Reply-To: <CAHmME9rU3AhppjN+6OM8vYHHbpK1Fxj2chVCCyHQBL-XvKk2uA@mail.gmail.com>
On 9/21/20 4:24 AM, Jason A. Donenfeld wrote:
> We've discussed this extensively and repeatedly. I made a few
> proposals a few years ago that we discussed. It doesn't fit into
> WireGuard's strong binding model.
>
> Jason
As I mentioned, I looked through the archives before starting this
thread. Specifically, I looked for mentions of multicast and followed
the threads, but I didn't find a concrete resolution. Maybe I missed
something.
I understand the theoretical argument. However, the practical
implication is that a widely deployed discovery mechanism on at least
one very population hardware platform is hamstrung without jumping
through pretty significant accounting hoops.
Given the other responses to this thread, it sounds like there is
interest in an opt-in feature but that a pull request would likely not
be accepted. Have I misunderstood?
~Derrick
next prev parent reply other threads:[~2020-09-21 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 7:13 Derrick Lyndon Pallas
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 [this message]
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=e5031f21-01ee-d3f1-fc27-4140fc1da363@pallas.us \
--to=derrick@pallas.us \
--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 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).