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 15:54:51 -0500 [thread overview]
Message-ID: <20160708205451.GA5959@wolff.to> (raw)
In-Reply-To: <CAHmME9ogt0izYi9_+3DqdEZAofLRE98fXdo1u7B581B0MknYUw@mail.gmail.com>
On Fri, Jul 08, 2016 at 22:21:09 +0200,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>On Fri, Jul 8, 2016 at 9:55 PM, Bruno Wolff III <bruno@wolff.to> wrote:
>> 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.
>
>I suspect you forgot to rmmod the previous module before trying this
>branch. There are no 0 length udp packets sent anywhere in this
>branch's code paths.
Yep, that was it. It allowed a remote connection at start up without
having to manually send traffic out locally first. So it looks like
it is working as expected.
Right now I am testing through a stateful firewall that blocks the
inbound connection unless it is related to an already established
connection. That isn't exactly the same as nat, but should work similarly
for testing purposes.
next prev parent reply other threads:[~2016-07-08 20: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
2016-07-08 20:21 ` Jason A. Donenfeld
2016-07-08 20:44 ` Bruno Wolff III
2016-07-08 20:54 ` Bruno Wolff III [this message]
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=20160708205451.GA5959@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox