On 7/20/20, Joachim Lindenberg wrote:
> Would be great to have the truth at https://www.wireguard.com/install/.
Looks like Andy has already fixed the problem.
> With the addition of bionic-proposed wireguard installs, but wg-quick fails
> because of "/usr/bin/wg-quick: line 32: resolvconf: comma
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 th
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 w
On Mon, Jul 20, 2020 at 5:15 PM Roman Mamedov wrote:
> Seems like it's available only starting from Ubuntu 19.10:
> https://packages.ubuntu.com/search?keywords=wireguard&searchon=names&suite=all§ion=all
It was added to 18.04, actually. See the other email I just sent.
On Mon, 20 Jul 2020 17:04:46 +0200
wrote:
> Yes, it is up to date.
> Joachim
>
> -Ursprüngliche Nachricht-
> Von: Jason A. Donenfeld
> Gesendet: Monday, 20 July 2020 16:49
> An: Joachim Lindenberg
> Cc: WireGuard mailing list
> Betreff: Re: Wireguard on Ubuntu 18.04.4 (LTS)?
>
> Is
Yes, it is up to date.
Joachim
-Ursprüngliche Nachricht-
Von: Jason A. Donenfeld
Gesendet: Monday, 20 July 2020 16:49
An: Joachim Lindenberg
Cc: WireGuard mailing list
Betreff: Re: Wireguard on Ubuntu 18.04.4 (LTS)?
Is your system fully up to date? `apt update && apt upgrade`?
Is your system fully up to date? `apt update && apt upgrade`?
Hello all,
I just tried to set up a new (virtual) machine with Ubuntu 18.04.4 (LTS) and
wireguard, but apt install wireguard reports “E: Unable to locate package
wireguard”. This is not really what I expect after looking at
https://www.wireguard.com/install/.
Any idea?
Thanks, Joachim
Hello,
thanks for pointing that out. Actually the idea was to switch over my VPN
endpoint from one VPS to another one, thus the any address route (0.0.0.0/0)
was correct, but now it is clear to me it does not make sense really to have
any address twice. I am trying to test the new endpoint with