Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Hayden Lau <lau.hayden@gmail.com>
To: F <finalcountdown@post.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Openresolv package is a requirement and should be added to install docs
Date: Thu, 28 Feb 2019 13:49:36 -0500	[thread overview]
Message-ID: <CAPN0m0zzQR2q-PW5CqtSsr9FNU9AXjT6ao7gihbuG8nPLxchKw@mail.gmail.com> (raw)
In-Reply-To: <304c3849-35d1-3312-1670-e7a8469a01fe@post.com>


[-- Attachment #1.1: Type: text/plain, Size: 821 bytes --]

On Thu, Feb 28, 2019 at 1:29 PM F <finalcountdown@post.com> wrote:
>
> Learnt how to get WG working here
> https://github.com/StreisandEffect/streisand/issues/1434 and it
> describes how the openresolv package is needed to get WG to connect
> properly. This is not noted in the official WG docs and the average
> person would have difficulty figuring out why wg-quick doesn't connect.

The openresolv package is not a dependency of WireGuard. WireGuard itself
does not deal with DNS - the wg-quick tool simply sets up DNS servers for
wg interfaces for convenience. For example, I use Ubuntu 18.04 on my
laptop, and that distro uses systemd-resolvd. Therefore, I add the line
'PostUp = systemd-resolve -i %i --set-dns=193.138.218.74 --set-domain=~' to
my config file instead of the 'DNS = [DNS server here]' line.

Hayden

[-- Attachment #1.2: Type: text/html, Size: 1194 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      parent reply	other threads:[~2019-03-01 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 13:26 F
2019-02-28 18:45 ` Reuben Martin
2019-03-01  8:14   ` Triffid Hunter
2019-03-01  9:35   ` Bjoern Franke
2019-02-28 18:49 ` Hayden Lau [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=CAPN0m0zzQR2q-PW5CqtSsr9FNU9AXjT6ao7gihbuG8nPLxchKw@mail.gmail.com \
    --to=lau.hayden@gmail.com \
    --cc=finalcountdown@post.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).