From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: [feature request] To support "Wireguard over raw TCP"
Date: Tue, 2 Oct 2018 08:40:21 +0200 [thread overview]
Message-ID: <75a25a9d-cf7d-1036-41b3-7d128d415b4a@urlichs.de> (raw)
In-Reply-To: <CACVet5Hm5HFDtNgTpk2q2r_8Qzt3xTH4sb63RcuyDTj7vdPacA@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 803 bytes --]
On 25.09.2018 18:29, Breus Blaauwendraad wrote:
> Could someone tell whether or not TCP would be a future additional
> option for WireGuard, and why (not)?
Which of the umpteen available/possible ways of encapsulating UDP
packets in TCP (and possibly obfuscating them in some way) would you
want Wireguard to natively implement?
The answer is simple: None of them. Bind to localhost, and use a
separate program for forwarding UDP packets.
Also: Any performance gain from supporting TCP natively (as opposed to
going through userspace) is easily dwarfed by the fact that congestion
control requires occasionally dropping packets – specifically, the
packets queued to the TCP socket. TCP cannot do that. Even more
complexity in the kernel? not likely.
--
-- Matthias Urlichs
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-10-02 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKVinOU6xpbJNfCPAecX7kOgk_PbCzThYtER9d3ax1h6k3DGTw@mail.gmail.com>
2018-09-25 15:52 ` StarBrilliant
2018-09-25 16:29 ` Breus Blaauwendraad
2018-10-02 6:40 ` Matthias Urlichs [this message]
2018-10-02 6:53 ` KeXianbin(http://diyism.com)
2018-10-02 9:00 ` KeXianbin(http://diyism.com)
[not found] ` <CAKVinOXXqMDRZcjVbOS4-iMBONdiYKaho8e3tEAZO+JKOZ_Gxw@mail.gmail.com>
2018-09-25 20:25 ` Michael Rash
2018-09-26 7:14 Saeid Akbari
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=75a25a9d-cf7d-1036-41b3-7d128d415b4a@urlichs.de \
--to=matthias@urlichs.de \
--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).