From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Wasa Bee <wasabee18@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: limitations
Date: Sat, 14 Jan 2017 21:52:19 +0100 [thread overview]
Message-ID: <CAHmME9rRcDj9W8an2JiQCuP_O9Wd3Neja6VwFntiTGbc845vcw@mail.gmail.com> (raw)
In-Reply-To: <CAOnWvx_BCaSO3i=319vCUjKuXG6E+8ReGsFGFFVgJLsdyb4RGg@mail.gmail.com>
On Sat, Jan 14, 2017 at 8:11 PM, Wasa Bee <wasabee18@gmail.com> wrote:
> - it is only over UDP. If so, is there ever going to be a TCP version? A lot
> of applications that could benefit from WG use TCP. It does not seem wise to
> expect programmers to implement a TCP-like layer (eg retransmission, ack,
> etc) in userspace, is it? This would increase complexity unnecessarily and
> would lead to vuln in practice...
I think you misunderstand. WireGuard is a layer 3 tunnel. Yes it uses
UDP and no it won't use TCP, but obviously you can use TCP sockets
over a layer 3 interface, just like you can with GRE or OpenVPN or
whatever else.
> - WG is implemented as a patch to the kernel or a kernel module? The reason
> I ask is that when an update is available for WG, it would be good not to
> have to replace the whole kernel, but only reload a patched WG module. Also:
> if there are ongoing sessions with some clients, how would sessions be
> re-established (afaik, the current design is to simply ignore irrelevant
> messages)?
Kernel module.
next prev parent reply other threads:[~2017-01-14 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 19:11 limitations Wasa Bee
2017-01-14 20:52 ` Jason A. Donenfeld [this message]
2017-01-14 20:55 ` limitations jens
2017-01-14 20:58 ` limitations Jason A. Donenfeld
2017-01-15 11:29 ` limitations Wasa Bee
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=CAHmME9rRcDj9W8an2JiQCuP_O9Wd3Neja6VwFntiTGbc845vcw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=wasabee18@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).