From: Triffid Hunter <triffid.hunter@gmail.com>
To: Reuben Martin <reuben.m.work@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Openresolv package is a requirement and should be added to install docs
Date: Fri, 1 Mar 2019 16:14:45 +0800 [thread overview]
Message-ID: <CACL3eKBUmeyUDUZXbPMPe_c6xFvAH7Y--6LdhSeU11+yoBDdWQ@mail.gmail.com> (raw)
In-Reply-To: <CALJ2VGZo9HYKyJt1=Or+DOhJgbOs1gs=XMECCLdfxN-dS325-Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]
I ran into this the other day, simply remove the DNS= line from your conf.
Probably should be documented that wg-quick will barf and tear down your
interface if you have DNS= but not `resolvconf` command.
On Fri, 1 Mar 2019 at 02:46, Reuben Martin <reuben.m.work@gmail.com> wrote:
> On Thu, Feb 28, 2019, 12: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
>>
>
> That may be a requirement in the context that document was written for.
> But that is not a requirement for wireguard.
>
>> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 1940 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev 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 Openresolv package is a requirement and should be added to install docs F
2019-02-28 18:45 ` Reuben Martin
2019-03-01 8:14 ` Triffid Hunter [this message]
2019-03-01 9:35 ` Bjoern Franke
2019-02-28 18:49 ` Hayden Lau
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=CACL3eKBUmeyUDUZXbPMPe_c6xFvAH7Y--6LdhSeU11+yoBDdWQ@mail.gmail.com \
--to=triffid.hunter@gmail.com \
--cc=reuben.m.work@gmail.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).