Wireguard now in Ubuntu distro repos across 16.04, 18.04, 19.10, 20.04

vimalware

Ref: my discovery post about wireguard on Ubuntu no longer needing a 3rd party PPA for installation : https://talk.lowendspirit.com/discussion/comment/35886/#Comment_35886

Wireguard is now in bionic-updates.
PPA+dkms no longer required for bionic users.

Apparently, there was an official announce by Jason Donenfeld (author) on the mailing list on the next day : Aug 3, 2020.

You can safely remove the PPA config from /etc/apt/sources.d/ if you were previously on it on the supported OSes.
https://lists.zx2c4.com/pipermail/wireguard/2020-August/005737.html

Hi folks,

At long last, Ubuntu now supports WireGuard on releases 20.04, 19.10,
18.04, and 16.04, which means we've got all currently supported LTS
releases covered. For that reason, we're in the process of sunsetting
the PPA that previously provided packages to some users. This email
details possible changes users might consider.

The right way to install WireGuard on Ubuntu now consists of a single
command:

$ sudo apt install wireguard

This "wireguard" package will automatically pull in either one or two
packages with it:

1) wireguard-tools: this will always be pulled in and provides wg(8)
and wg-quick(8).
2) wireguard-dkms: this will only be pulled in if your kernel doesn't
already come with WireGuard.

As suggested by (2), most Ubuntu kernels now come with WireGuard out of
the box, even older releases, to which WireGuard has been backported.
This is great news and will result in much better reliability during
upgrades, as well as smoother compatibility with SecureBoot.

--snipped--

As a very good general recommendation for people new to wireguard ,
USE https://github.com/Nyr/wireguard-install/ (read the README first)

I have reviewed nyr's wireguard-install script and I am satisfied that it is well done.
I compared it with a manually configured wireguard tunnel, and all the defaults seem sensible.
Anything that saves you time should be welcomed.
Shoutout to @nyr, a long time LET/S MVP.

Nyr

Thanks for the mention, because I was on vacation and didn't notice this. Will update the script very soon.

AlwaysSkint

Still won't persuade me to install Ubuntu on a server (rather than CentOS or debian).

SuriCloud

@Nyr said:
Thanks for the mention, because I was on vacation and didn't notice this. Will update the script very soon.

Let us know how to update in already installed vps.

vimalware

@SuriCloud said:

@Nyr said:
Thanks for the mention, because I was on vacation and didn't notice this. Will update the script very soon.

Let us know how to update in already installed vps.

I believe nyr is referring to the script currently using the ppa as the package source.

If you are on one of these supported Ubuntu versions, you just have to remove the .list file corresponding to the wireguard-ppa from /etc/apt/sources.list.d/

Then after running an apt update, double-check with apt-cache policy wireguard .
It should list a wireguard candidate package , assuming bionic-updates is enabled (the default)

Worked fine here.

flips

In other news, Wireguard support in Mikrotik RouterOS:

What's new in 7.1beta2:

• added WireGuard support
• other stuff ...

From Twitter.

(I posted this in the pit, @beagle meant it could fit here as well ... I initially didn't want to de-rail a Ubuntu thread.)

seanho

Debian bullseye also uses kernel 5.7, which includes wireguard in-tree (as of 5.6), so no dkms needed.

vimalware

@seanho said:
Debian bullseye also uses kernel 5.7, which includes wireguard in-tree (as of 5.6), so no dkms needed.

Exciting, but the dates seem so distant.
https://release.debian.org/bullseye/freeze_policy.html
Corona casualty, I suppose.

If Canonical doesn't sort out their snap store BS policies by then, 16.04 LTS boxes are going straight to bullseye I think.

seanho

There's always buster-backports, too. My laptop is running buster but with the backports kernel, in-tree wireguard, managed by systemd-networkd.

AaronSS

@Nyr said: Will update the script very soon.

Any updates?

vimalware

@aaronstuder said:

@Nyr said: Will update the script very soon.

Any updates?

One could just comment out the lines that import the ppa. The script would use the distro package then (same package name) ?

Nyr

@aaronstuder said: Any updates?

It is a little bit more involved than removing the PPA, but you can probably do as @vimalware suggested for your personal usage.

I hope to push the update within the next 24 hours, I have that ready and just some testing needs to be done before that.

Nyr

wireguard-install has now been updated.

Apologies for the delay.

bdl

@Nyr said:
wireguard-install has now been updated.

Apologies for the delay.

Thank you @Nyr

chocolateshirt

@Nyr said:
wireguard-install has now been updated.

Apologies for the delay.

Do we need to uninstall the old wireguard script? Then reinstall the latest one?

deepak_leb

@chocolateshirt said:

@Nyr said:
wireguard-install has now been updated.

Apologies for the delay.

Do we need to uninstall the old wireguard script? Then reinstall the latest one?

Yeah same doubt ?

bdl

If you look at the diff's of the script, no real need to reinstall the latest one if your current one is working fine

Nyr

@chocolateshirt @deepak_leb

Instructions for removing the PPA here:

https://lists.zx2c4.com/pipermail/wireguard/2020-August/005737.html

No need to reinstall.

chocolateshirt

@Nyr said:
@chocolateshirt @deepak_leb

Instructions for removing the PPA here:

https://lists.zx2c4.com/pipermail/wireguard/2020-August/005737.html

No need to reinstall.

somik

Just yesterday I installed wireguard from PPA... WHY!!!!!

vimalware

It's ok. Just delete the ppa's .list file, and purge wireguard-dkms package to be sure.

You should then be all set after a dist-upgrade.