All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] [ANNOUNCE] Snapshot `experimental-0.0.20160708.1` Available
Date: Fri, 8 Jul 2016 14:55:07 -0500	[thread overview]
Message-ID: <20160708195507.GA1990@wolff.to> (raw)
In-Reply-To: <CAHmME9o0RrpbUBB7nBQ319d_0pragpf94jFX0ZCGdMX9W8T1ug@mail.gmail.com>

On Fri, Jul 08, 2016 at 20:49:07 +0200,
  "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>On Fri, Jul 8, 2016 at 7:55 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>> But is it too fragile? Maybe we should scrap all of this and make
>> persistent keepalives authenticated. I'm not too thrilled about that
>> though...
>
>I'm experimenting with this in the authenticated-persistent-keepalive
>branch, if you'd like to try it out and report back on how it goes...

It looks like initially it does 0 length udp packets for keep alive and the 
authenticated keep alives don't seem to happen until after some data is sent.

  reply	other threads:[~2016-07-08 19:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 14:37 [WireGuard] [ANNOUNCE] Snapshot `experimental-0.0.20160708.1` Available Jason A. Donenfeld
2016-07-08 16:23 ` Bruno Wolff III
2016-07-08 17:55   ` Jason A. Donenfeld
2016-07-08 18:49     ` Jason A. Donenfeld
2016-07-08 19:55       ` Bruno Wolff III [this message]
2016-07-08 20:21         ` Jason A. Donenfeld
2016-07-08 20:44           ` Bruno Wolff III
2016-07-08 20:54           ` Bruno Wolff III
2016-07-08 21:45             ` Jason A. Donenfeld

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=20160708195507.GA1990@wolff.to \
    --to=bruno@wolff.to \
    --cc=Jason@zx2c4.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 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.