From: dan <dandenson@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: wireguard + udpspeeder or tinyfecvpn or similar fec
Date: Sat, 8 Dec 2018 09:13:37 -0700 [thread overview]
Message-ID: <CAA_JP8V_KLNg68jObQx=Vxb+Sd12-x6swsqt9PzWuoRi6eGpEA@mail.gmail.com> (raw)
Is there any consideration being given to adding fec to wireguard?
udpspeeder and tinyfecvpn are good examples here but they lack
essentially everything that makes wireguard great.
It's not ideal to run udpspeeder first and then wireguard over the top
because you lose wireguards roaming capabilities and more.
It's not ideal to run udpspeeder over a wireguard tunnel because it's
basically just hard to utilize.
it's *wierd* to establish a wireguard tunnel, then a udpspeeder
tunnel, and then another wireguard tunnel on top of that. too many
layers, chopping down MTU too much to make it happen.
it would be fantastic to have wireguard integrate some fec
capabilities natively.
I know that simplicity is a big part of this, but it's not a very
reasonable option to stack this stuff up in layers as that's
substantially higher complexity.
tinyfecvpn is a layer3 tunnel on top of udp speeder. you can do
wireguard then tinyfecvpn on top which is somewhat simple *BUT*
tinyfecvpn is kind of a loose utility without a decent suite of tools
to maintain things.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-01-02 17:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA_JP8V_KLNg68jObQx=Vxb+Sd12-x6swsqt9PzWuoRi6eGpEA@mail.gmail.com' \
--to=dandenson@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;
as well as URLs for NNTP newsgroup(s).