Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Lee Yates <rainmakerraw@icloud.com>
Cc: "WireGuard@lists.zx2c4.com" <WireGuard@lists.zx2c4.com>
Subject: Re: DNS fails after undetermined time in-tunnel
Date: Fri, 3 Jan 2020 16:54:30 +0100	[thread overview]
Message-ID: <CAHmME9r9HnJWc+_8tEoDKNtd6QrhRKP_nTZSaJ4TGVW5+bhm3Q@mail.gmail.com> (raw)
In-Reply-To: <eae1d28d-bcf2-8e42-93e9-2b6c5879e28c@icloud.com>

Interesting bug. According to the man page, the -u should already be
implicit when doing -a, since the contents should be different.

Can you look to see where in the resolvconf script it bails out? Maybe
stick a `set -x` at the top or something similar?
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2020-01-03 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31 18:49 Lee Yates
2019-12-31 19:24 ` Lee Yates
2020-01-03 15:54   ` Jason A. Donenfeld [this message]

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=CAHmME9r9HnJWc+_8tEoDKNtd6QrhRKP_nTZSaJ4TGVW5+bhm3Q@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=WireGuard@lists.zx2c4.com \
    --cc=rainmakerraw@icloud.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).