mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: bruno@wolff.to
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] WireGuard: next generation secure network tunnel
Date: Sat, 2 Jul 2016 01:03:17 +0200	[thread overview]
Message-ID: <b41c6b79-1c62-b3b2-4f8f-71a53e2babc4@zx2c4.com> (raw)
In-Reply-To: <CAHmME9q-6ioctzcB8gLdYOsMFqHVGY8GUsVGFisKv=wGdVqi2A@mail.gmail.com>

Hey Bruno,

Sorry I didn't reply to this earlier; the message didn't make it to me
somehow.

Bruno Wolff III <bruno@wolff.to> writes:
> 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.

Happy to hear!

>
> 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.

That seems like a setup that would work fine.

>
> This seems much easier to use than ipsec and should be faster than
> tunnelling over ssh or openvpn.

Absolutely! That's the goal.

Thanks for the feedback,
Jason

  parent reply	other threads:[~2016-07-01 23:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 14:49 Jason A. Donenfeld
2016-06-30  0:34 ` Bruno Wolff III
2016-07-01 11:42 ` Richard Weinberger
2016-07-01 14:25   ` Jason A. Donenfeld
2016-07-01 14:47     ` Richard Weinberger
2016-07-01 23:03 ` Jason A. Donenfeld [this message]
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=b41c6b79-1c62-b3b2-4f8f-71a53e2babc4@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®