From: Bruno Wolff III <bruno@wolff.to>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] WireGuard: next generation secure network tunnel
Date: Wed, 29 Jun 2016 19:34:58 -0500 [thread overview]
Message-ID: <20160630003458.GA7581@wolff.to> (raw)
In-Reply-To: <CAHmME9q-6ioctzcB8gLdYOsMFqHVGY8GUsVGFisKv=wGdVqi2A@mail.gmail.com>
On Tue, Jun 28, 2016 at 16:49:18 +0200,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>
>Today I'm releasing WireGuard, an encrypted and authenticated
>tunneling virtual interface for the kernel. It uses next-generation
I tried this out on 4.7 kernels and it seemed to work OK. I can't tell
about security, but the packets made it to where they are going.
My eventual use case, is to be able to reach a machine behind NAT by going
though a fixed machine in another location. The machine behind NAT will
keep a tunnel usable by occasionally pinging through the tunnel to make
sure that NAT has state information allowing packets to make it back and
that the fixed machine knows where to send packets.
This seems much easier to use than ipsec and should be faster than
tunnelling over ssh or openvpn.
next prev parent reply other threads:[~2016-06-30 0:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 14:49 [RFC] WireGuard: next generation secure network tunnel Jason A. Donenfeld
2016-06-30 0:34 ` Bruno Wolff III [this message]
2016-07-01 11:42 ` Richard Weinberger
2016-07-01 13:50 ` Matthias Urlichs
2016-07-01 14:25 ` Jason A. Donenfeld
2016-07-01 14:47 ` Richard Weinberger
2016-07-01 23:03 ` Jason A. Donenfeld
2016-07-01 23:42 ` Bruno Wolff III
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=20160630003458.GA7581@wolff.to \
--to=bruno@wolff.to \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.