From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Should I expect faster recovery after one side goes down
Date: Mon, 27 Nov 2017 12:25:58 -0600 [thread overview]
Message-ID: <20171127182558.GA19220@wolff.to> (raw)
In-Reply-To: <CAHmME9rq+eaLMZP+a1OAcu1=65X7Q_PrsMNBwAm7U2HaNWfUVQ@mail.gmail.com>
On Mon, Nov 27, 2017 at 18:36:23 +0100,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>Hello Bruno,
>
>That's some pretty weird behavior, and it sounds like whatever the
>cause is is being obscured under layers of systemd. Perhaps come on
>into #wireguard on Freenode and we can debug this in real time? I've
>got a few ideas.
I don't have my laptop with me at work and breaking the wireguard tunnel
to it will break my access to it from here. I could check configuration
from work. I can bring it with me tomorrow, otherwise I'll probably get
home too late for you tonight and I probably won't be up late enough
to catch you early tomorrow.
Probably I'll be able to reproduce the issue from work.
next prev parent reply other threads:[~2017-11-27 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 9:49 Should I expect faster recovery after one side goes down Bruno Wolff III
2017-11-27 11:04 ` Jason A. Donenfeld
2017-11-27 13:49 ` Bruno Wolff III
2017-11-27 17:33 ` Bruno Wolff III
2017-11-27 17:36 ` Jason A. Donenfeld
2017-11-27 18:25 ` Bruno Wolff III [this message]
2017-11-28 6:13 ` Bruno Wolff III
2017-11-28 6:44 ` Bruno Wolff III
2017-11-28 8:42 ` Bruno Wolff III
2017-12-01 8:43 ` Baptiste Jonglez
2017-12-01 17:02 ` 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=20171127182558.GA19220@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.