Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "M. Dietrich" <mdt@emdete.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Defaultroutepiercing
Date: Thu, 18 Jan 2018 15:20:08 +0100	[thread overview]
Message-ID: <CAHmME9oh74ca=PZFe2oK9rvqBZW15Ntmz=e-rnxMYqhG9k8ZAg@mail.gmail.com> (raw)
In-Reply-To: <1516283661.uwaeedz44a.astroid@morple.none>

On Thu, Jan 18, 2018 at 3:11 PM, M. Dietrich <mdt@emdete.de> wrote:
>         [#] resolvconf -a tun.wg0 -m 0 -x
>
> which seems to be wrong, the manpage resolvconf(8) states that the
> this parameter is
>
>         interface[.protocol]
>
> why is "tun." prepended?

To hack around incompetence on the part of Debian. They order entries
based on the device prefix.

If you have something custom going on, use PostUp/PostDown or
PreUp/PreDown to call your custom script, instead of using DNS=.

> the command is issued before the routing is configured.
> shouldnt the DNS configuration be applied after routing
> changes?

I can reason about it in both directions. What's your intuition lead
you to the _after_ choice?

  reply	other threads:[~2018-01-18 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 13:00 Defaultroutepiercing M. Dietrich
2018-01-18 13:02 ` Defaultroutepiercing Jason A. Donenfeld
2018-01-18 14:11   ` Defaultroutepiercing M. Dietrich
2018-01-18 14:20     ` Jason A. Donenfeld [this message]
2018-01-18 14:44       ` Defaultroutepiercing M. Dietrich

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='CAHmME9oh74ca=PZFe2oK9rvqBZW15Ntmz=e-rnxMYqhG9k8ZAg@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=mdt@emdete.de \
    --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).