From: Roman Mamedov <rm@romanrm.net>
To: netravnen@gmail.com
Cc: wireguard@lists.zx2c4.com
Subject: Re: Getting IPv6 route advertisements to work over WG
Date: Mon, 27 Aug 2018 18:53:29 +0500 [thread overview]
Message-ID: <20180827185329.1a7bb24a@natsu> (raw)
In-Reply-To: <8c7ad33a-b1bc-1993-e442-836230f4bf37@gmail.com>
On Mon, 27 Aug 2018 15:32:49 +0200
netravnen@gmail.com wrote:
> When using multicast over WireGuard, would it not be more viable to use
> an extra encapsulation layer to run multicast inside of?
>
> I am specifically thinking of running either GRE or L2TPv3 over wgX.
I know people run VXLAN or other L2 tunneling protocols over WG. I suppose
you can call that "viable" as in "it can work", but it's a horrible workaround
for the lack of better solution, nothing more. For instance the overhead
reaches comical levels:
TCP
over IP
over Ethernet
over VXLAN
over UDP
over IP
over Wireguard
over UDP
over IP
over Ethernet
Add more fun if you use something else such as PPPoE for Internet connection,
or a 6in4 tunnel for IPv6. At some point the whole thing will break down
because you can no longer fit 1280-byte packets into innermost MTU, and IPv6
won't work.
Not to mention the additional management overhead of an inner L2 tunneling
layer.
Now, if WG would support L2 mode natively (say, with AllowedMACs instead of
AllowedIPs) it would be awesome and that would solve a great number of other
issues as well. But since that appears to be unlikely, and since RAs already
mostly work, with just one piece missing, I hope at least that piece gets
dropped in at some point, and that we aren't stuck at least for this use case
with "more viable" tunneling workarounds forever.
--
With respect,
Roman
next prev parent reply other threads:[~2018-08-27 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 12:14 Getting IPv6 route advertisements to work over WG Roman Mamedov
2018-08-27 13:32 ` netravnen
2018-08-27 13:53 ` Roman Mamedov [this message]
2018-08-27 14:46 ` Riccardo Paolo Bestetti
2018-08-27 14:55 ` Matthias Urlichs
2018-08-27 21:14 ` StarBrilliant
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=20180827185329.1a7bb24a@natsu \
--to=rm@romanrm.net \
--cc=netravnen@gmail.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