From: "Joachim Lindenberg" <wireguard@lindenberg.one>
To: "'Jason A. Donenfeld'" <Jason@zx2c4.com>,
"'Joachim Lindenberg'" <wireguard@lindenberg.one>
Cc: "'WireGuard mailing list'" <wireguard@lists.zx2c4.com>,
"'Andy Whitcroft'" <apw@canonical.com>
Subject: AW: Wireguard on Ubuntu 18.04.4 (LTS)?
Date: Mon, 20 Jul 2020 17:51:59 +0200 [thread overview]
Message-ID: <076601d65ead$b4094d70$1c1be850$@lindenberg.one> (raw)
In-Reply-To: <CAHmME9pyp7z7043ZwvRv0huy9n1zL3x6O7o4w5EsQdg5WsOsdQ@mail.gmail.com>
Would be great to have the truth at https://www.wireguard.com/install/.
With the addition of bionic-proposed wireguard installs, but wg-quick fails because of "/usr/bin/wg-quick: line 32: resolvconf: command not found". Looks like a dependency is not set.
Which of openresolv or resolvconf is the recommended path?
Thanks, Joachim
-----Ursprüngliche Nachricht-----
Von: Jason A. Donenfeld <Jason@zx2c4.com>
Gesendet: Monday, 20 July 2020 17:22
An: Joachim Lindenberg <wireguard@lindenberg.one>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>; Andy Whitcroft <apw@canonical.com>
Betreff: Re: Wireguard on Ubuntu 18.04.4 (LTS)?
Looks like at the moment (July 20, 2020; ignore this email if you're reading this >1 month from now) wireguard is still stuck in -proposed on Bionic.
echo 'deb http://us.archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse' >> /etc/apt/sources.list apt update apt install wireguard
That's annoying and odd. I'm CCing Canonical's Andy Whitcroft who can fix this inside of Ubuntu.
next prev parent reply other threads:[~2020-07-20 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 14:29 wireguard
2020-07-20 14:48 ` Jason A. Donenfeld
2020-07-20 15:04 ` AW: " wireguard
2020-07-20 15:14 ` Roman Mamedov
2020-07-20 15:22 ` Jason A. Donenfeld
2020-07-21 12:42 ` Jason A. Donenfeld
2020-07-21 12:48 ` Jasper Knockaert
2020-07-21 12:57 ` Jason A. Donenfeld
2020-07-20 15:22 ` Jason A. Donenfeld
2020-07-20 15:51 ` Joachim Lindenberg [this message]
2020-07-20 21:59 ` Jason A. Donenfeld
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='076601d65ead$b4094d70$1c1be850$@lindenberg.one' \
--to=wireguard@lindenberg.one \
--cc=Jason@zx2c4.com \
--cc=apw@canonical.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).