Development discussion of WireGuard
 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: Should I expect faster recovery after one side goes down
Date: Mon, 27 Nov 2017 07:49:14 -0600	[thread overview]
Message-ID: <20171127134914.GA9392@wolff.to> (raw)
In-Reply-To: <CAHmME9q+giuOXVz1=hE-F34vFMP0GxzveMzLbzrjeXbbjnrGCQ@mail.gmail.com>

On Mon, Nov 27, 2017 at 12:04:06 +0100,
  "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>Hi Bruno,
>
>The first question is - how long?

For "systemctl iptables stop" I have waited around a minute before 
using control C. After running "systemctl stop wireguard" or 
"systemctl restart wireguard" (which will delete wg0) "systemctl stop 
iptables" will run with no noticeable delay.

For network traffic, I waited around 10 minutes and things were still not 
working. Web page loads would still time out after a minute or two. But 
I did have a few DNS lookups succeed. I'm not sure if I did something 
that allowed a value to get cached (there is a local caching resolver 
on the affected machines) or if a response eventually made it through. 
After "systemctl restart wireguard" things start working normal right 
away. So I don't know the delay for specific traffic, but it looks to 
be at least a minute for most traffic. The problem does not seem to 
resolve for at least 10 minutes, though I don't think I have ever seen it 
resolve on its own.

  reply	other threads:[~2017-11-27 13:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27  9:49 Bruno Wolff III
2017-11-27 11:04 ` Jason A. Donenfeld
2017-11-27 13:49   ` Bruno Wolff III [this message]
2017-11-27 17:33     ` Bruno Wolff III
2017-11-27 17:36       ` Jason A. Donenfeld
2017-11-27 18:25         ` Bruno Wolff III
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=20171127134914.GA9392@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;
as well as URLs for NNTP newsgroup(s).