DietPi-Software | WireGuard: Raise APT package priority pin to 100 to allow auto upgrades

[swrobel]

ADMIN EDIT

Solution

sed -i 's/Pin-Priority: 99/Pin-Priority: 100/' /etc/apt/preferences.d/dietpi-wireguard
G_AGUP
G_AGUG

---

Required Information

• DietPi version | cat /DietPi/dietpi/.version
  G_DIETPI_VERSION_CORE=6
  G_DIETPI_VERSION_SUB=22
  G_DIETPI_VERSION_RC=3
  G_GITBRANCH=master
  G_GITOWNER=Fourdee
• Distro version | echo $G_DISTRO_NAME or cat /etc/debian_version
  stretch
• Kernel version | uname -a
  Linux DietPi 4.14.98-v7+ Request | RT Kernel option #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux
• SBC device | echo $G_HW_MODEL_DESCRIPTION or (EG: RPi3)
  RPi 3 Model B+ (armv7l)
• Power supply used | (EG: 5V 1A RAVpower)
  5V 2.1A iPad charger
• SDcard used | (EG: SanDisk ultra)
  SanDisk

Additional Information (if applicable)

• Software title | Wireguard
• Was the software title installed freshly or updated/migrated? Updated
• Can this issue be replicated on a fresh installation of DietPi? Most likely not
• dietpi-bugreport ID | bfa7faf1-0e3d-404b-b1dc-fa8da172aa5b

Steps to reproduce

root@DietPi:~# systemctl start wg-quick@wg0
Job for [email protected] failed because the control process exited with error code.
See "systemctl status [email protected]" and "journalctl -xe" for details.
root@DietPi:~# systemctl status wg-quick@wg0
● [email protected] - WireGuard via wg-quick(8) for wg0
   Loaded: loaded (/lib/systemd/system/[email protected]; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-03-27 22:01:05 GMT; 5s ago
     Docs: man:wg-quick(8)
           man:wg(8)
           https://www.wireguard.com/
           https://www.wireguard.com/quickstart/
           https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick.8
           https://git.zx2c4.com/WireGuard/about/src/tools/man/wg.8
  Process: 2191 ExecStart=/usr/bin/wg-quick up wg0 (code=exited, status=1/FAILURE)
 Main PID: 2191 (code=exited, status=1/FAILURE)

Mar 27 22:01:05 DietPi systemd[1]: Starting WireGuard via wg-quick(8) for wg0...
Mar 27 22:01:05 DietPi wg-quick[2191]: [#] ip link add wg0 type wireguard
Mar 27 22:01:05 DietPi wg-quick[2191]: RTNETLINK answers: Operation not supported
Mar 27 22:01:05 DietPi wg-quick[2191]: Unable to access interface: Protocol not supported
Mar 27 22:01:05 DietPi wg-quick[2191]: [#] ip link delete dev wg0
Mar 27 22:01:05 DietPi wg-quick[2191]: Cannot find device "wg0"
Mar 27 22:01:05 DietPi systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Mar 27 22:01:05 DietPi systemd[1]: Failed to start WireGuard via wg-quick(8) for wg0.
Mar 27 22:01:05 DietPi systemd[1]: [email protected]: Unit entered failed state.
Mar 27 22:01:05 DietPi systemd[1]: [email protected]: Failed with result 'exit-code'.

Expected behaviour

Wireguard should start as it did before

Actual behaviour

Wireguard will not start, even after a reboot

Extra details

It does not seem the wireguard kmod is loaded:

root@DietPi:~# lsmod
Module                  Size  Used by
sg                     28672  0
uas                    24576  0
uio_pdrv_genirq        16384  0
uio                    20480  1 uio_pdrv_genirq
fixed                  16384  0
ip_tables              24576  0
x_tables               32768  1 ip_tables
ipv6                  425984  27

However I believe all necessary packages are installed:

root@DietPi:~# dpkg -l | grep wireguard
ii  wireguard                     0.0.20181218-1               all          fast, modern, secure kernel VPN tunnel (metapackage)
ii  wireguard-dkms                0.0.20181218-1               all          fast, modern, secure kernel VPN tunnel (DKMS version)
ii  wireguard-tools               0.0.20181218-1               armhf        fast, modern, secure kernel VPN tunnel (userland utilities)

[MichaIng]

@swrobel
Many thanks for your report.

Most likely the kernel was upgraded but not the WireGuard kernel module. I also see that the package version is not the up-to-date: https://packages.debian.org/sid/wireguard

Looks like it was not auto-upgraded.

Could you try:
apt upgrade
Check if the WireGuard packages are upgraded as well. If not run:
apt full-upgrade
Check if the WireGuard packages are upgraded as well. If not run:
apt install wireguard wireguard-dkms wireguard-tools
The last should force installing the packages regardless of repo priorities.

Please report back which step did the WireGuard upgrade. It will include a rebuild of the module against the current kernel version.

Sorry me are dump. Installed packages have the priority 100 and we pinned WireGuard packages to priority 99...
Please do:

sed -i 's/Pin-Priority: 99/Pin-Priority: 100/' /etc/apt/preferences.d/dietpi-wireguard
G_AGUP
G_AGUG

• The WireGuard packages should be upgraded as well with this, triggering a module rebuild against the current kernel version.

---

Generally if your kernel is upgraded, on RPi you will face a long APT upgrade run with many messages that contain "rpikernelhack", then the WireGuard module needs to be rebuild.

On x86_64 systems due to my tests, a kernel upgrade triggered this automatically. On RPi this seems to be not the case, so you need to do that manually.

As above, there is a WireGuard update available as well, so upgrading as above will force a kernel module rebuild now. But if there is no WireGuard upgrade available when doing a kernel upgrade, you need to run:
dpkg-reconfigure wireguard-dkms
to rebuild the module.

[swrobel]

Thanks, that worked!

[MichaIng]

Fix is handled here: #2700