WireGuard Update failes Topic is solved

[Joulinar]

and did you checked the log file??

Code: Select all

Consult /var/lib/dkms/wireguard/1.0.20200506/build/make.log for more information.

[Niwre]

@Joulinar

Here is the content from the log file

DKMS make.log for wireguard-1.0.20200506 for kernel 4.9.0-9-amd64 (x86_64)
Di 19. Mai 19:45:22 BST 2020
make: Verzeichnis „/usr/src/linux-headers-4.9.0-9-amd64“ wird betreten
LD /var/lib/dkms/wireguard/1.0.20200506/build/built-in.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/main.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/noise.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/device.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/peer.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/timers.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/queueing.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/send.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/receive.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/socket.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/peerlookup.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/allowedips.o
CC [M] /var/lib/dkms/wireguard/1.0.20200506/build/ratelimiter.o
/var/lib/dkms/wireguard/1.0.20200506/build/ratelimiter.c:25:8: error: unknown type name ‘hsiphash_key_t’
static hsiphash_key_t key;
^~~~~~~~~~~~~~
/var/lib/dkms/wireguard/1.0.20200506/build/ratelimiter.c: In function ‘wg_ratelimiter_allow’:
/var/lib/dkms/wireguard/1.0.20200506/build/ratelimiter.c:109:22: error: implicit declaration of function ‘hsiphash_2u32’ [-Werror=implicit-function-declaration]
bucket = &table_v4[hsiphash_2u32(net_word, ip, &key) &
^~~~~~~~~~~~~
/var/lib/dkms/wireguard/1.0.20200506/build/ratelimiter.c:116:22: error: implicit declaration of function ‘hsiphash_3u32’ [-Werror=implicit-function-declaration]
bucket = &table_v6[hsiphash_3u32(net_word, ip >> 32, ip, &key) &
^~~~~~~~~~~~~
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.9.0-9-common/scripts/Makefile.build:309: die Regel für Ziel „/var/lib/dkms/wireguard/1.0.20200506/build/ratelimiter.o“ scheiterte
make[3]: *** [/var/lib/dkms/wireguard/1.0.20200506/build/ratelimiter.o] Fehler 1
/usr/src/linux-headers-4.9.0-9-common/Makefile die Regel für Ziel „_module_/var/lib/dkms/wireguard/1.0.20200506/build“ scheiterte
make[2]: *** [_module_/var/lib/dkms/wireguard/1.0.20200506/build] Fehler 2
Makefile:152: die Regel für Ziel „sub-make“ scheiterte
make[1]: *** [sub-make] Fehler 2
Makefile:8: die Regel für Ziel „all“ scheiterte
make: *** [all] Fehler 2
make: Verzeichnis „/usr/src/linux-headers-4.9.0-9-amd64“ wird verlassen

[Joulinar]

ok found a similar report on the web fitting yours

https://bugs.debian.org/cgi-bin/bugrepo ... bug=935134

it's not the same version of wireguard but fitting your kernel 4.9.0-9-amd64.

EDIT: your kernel seems not the latest one. On my test system I can see 4.9.0-12-amd64

Code: Select all

root@DietPiVM3:~# uname -a
Linux DietPiVM3 4.9.0-12-amd64 #1 SMP Debian 4.9.210-1 (2020-01-20) x86_64 GNU/Linux
root@DietPiVM3:~#

[Niwre]

@Joulinar

That seems to be the problem, but what can I do now? I don't really understand the linked post.

Code: Select all

 root@WireGuardPi:~# uname -a
Linux WireGuardPi 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux

[Joulinar]

I guess you would need to update your kernel. Usually this should happen automatically by running apt update && apt upgrade

I assume you are running debian Stretch. Correct?

[Niwre]

@Joulinar

Yes, I'm on Debian Stretch. I tried again with apt update && apt upgrade, unfortunately the kernel is not updated.

[Joulinar]

are you running a VM or physical box? Just as interest because I see x86?

What else you are running on your system? Anything in addition?

[Niwre]

@Joulinar

I use a VM on an ESXi 6.0, the VM is only used for WireGuard.

[Joulinar]

ok in this case, I would recommend to create a new VM on Buster as Stretch is the old Debian version. It will be much faster and shorter instead of figuring out what happen and why the kernel did not update. Next to this Buster is more future proof than continue running Stretch.

You just would need to safe your configs on /etc/wireguard. Once you finished setup and installation on the new Buster systems, simply copy back the files and restart wireguard. I did the same in the past and it was working quite well.

[Niwre]

@Joulinar

Is there a finished image for Debian Buster as a VM that I can use as a basis for it?