First off: this is not a duplicate. I've tried everything except OpenVPN or IPSec. I'm receiving a handshake between the client and server, and SSH and Ping work between clients, but I cannot access the global internet or even have access to the server's public IP. My config is just the usual, keys, endpoints, I followed the Linode guide exactly. My client is openSUSE but my server is ubuntu, which I'm assuming is the chokepoint.
Hello I am very new to ubuntu, I installed wireguard almost 6 months ago, and it was working fine, untill yesterday when my ubuntu was updated, the wirguard does not want to come up, and gives the below status:
May 31 08:41:03 lenovo systemd[1]: Starting WireGuard via wg-quick(8) for wg0...
May 31 08:41:03 lenovo wg-quick[5463]: [#] ip link add wg0 type wireguard
May 31 08:41:03 lenovo wg-quick[5463]: Error: Unknown device type.
May 31 08:41:03 lenovo wg-quick[5463]: Unable to access interface: Protocol not supported
May 31 08:41:03 lenovo wg-quick[5463]: [#] ip link delete dev wg0
May 31 08:41:03 lenovo wg-quick[5463]: Cannot find device "wg0"
May 31 08:41:03 lenovo systemd[1]: [email protected]: Main process exited, code=exited,
status=1/FAILURE
May 31 08:41:03 lenovo systemd[1]: [email protected]: Failed with result 'exit-code'.
May 31 08:41:03 lenovo systemd[1]: Failed to start WireGuard via wg-quick(8) for wg0.
here is my ubuntu version: Ubuntu 18.04.4 LTS
I ran updates and upgrades today and couldn't get WireGuard up:
$ sudo wg-quick up wg0
[#] ip link add wg0 type wireguard
Error: Unknown device type.
Unable to access interface: Protocol not supported
Purging and reinstalling WireGuard results in:
Setting up wireguard-dkms (1.0.20200429-2~18.04) ...
Loading new wireguard-1.0.20200429 DKMS files...
Building for 5.3.0-53-generic
Building initial module for 5.3.0-53-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/wireguard-dkms.0.crash'
Error! Bad return status for module build on kernel: 5.3.0-53-generic (x86_64)
Consult /var/lib/dkms/wireguard/1.0.20200429/build/make.log for more information.
Setting up wireguard-tools (1.0.20200513-1~18.04) ...
wg-quick.target is a disabled or a static unit, not starting it.
Setting up wireguard (1.0.20200513-1~18.04) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
ProblemType: Package
DKMSBuildLog:
DKMS make.log for wireguard-1.0.20200429 for kernel 5.3.0-53-generic (x86_64)
Wed May 20 09:54:57 PDT 2020
make: Entering directory '/usr/src/linux-headers-5.3.0-53-generic'
CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/main.o
CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/noise.o
CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/device.o
CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/peer.o
CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/timers.o
CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/queueing.o
CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/receive.o
CC [M] /var/lib/dkms/wireguard/1.0.20200429/build/send.o
In file included from <command-line>:0:0:
/var/lib/dkms/wireguard/1.0.20200429/build/compat/compat.h:1024:20: error: redefinition of ‘skb_reset_redirect’
static inline void skb_reset_redirect(struct sk_buff *skb)
^~~~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/wireguard/1.0.20200429/build/compat/compat.h:870:0,
from <command-line>:0:
./include/linux/skbuff.h:4476:20: note: previous definition of ‘skb_reset_redirect’ was here
static inline void skb_reset_redirect(struct sk_buff *skb)
^~~~~~~~~~~~~~~~~~
In file included from <command-line>:0:0:
/var/lib/dkms/wireguard/1.0.20200429/build/compat/compat.h:1024:20: error: redefinition of ‘skb_reset_redirect’
static inline void skb_reset_redirect(struct sk_buff *skb)
Originally, I installed it with ppa:wireguard/wireguard - is the install different now with this kernel?
I have already running 12 WireGuard VPN Servers.
Now I want to use an application to manage the connection on the clients.
On my Arch-Linux Client I have the network-manager-wireguard plugin running and its working fine.
Is there any WireGuard GUI for Ubuntu?
I am running Ubuntu 20.04 and already tried to compile this https://github.com/max-moser/network-manager-wireguard myself, but I ran into the following error during ./autogen.sh:
checking for LIBNM_GLIB... no
configure: error: Package requirements (NetworkManager >= 1.2.0
libnm-util >= 1.2.0
libnm-glib >= 1.2.0
libnm-glib-vpn >= 1.2.0) were not met:
No package 'NetworkManager' found
No package 'libnm-util' found
No package 'libnm-glib' found
No package 'libnm-glib-vpn' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBNM_GLIB_CFLAGS
and LIBNM_GLIB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
But, I can't find the packages libnm-util, libnm-glib and libnm-glib-vpn in the package repositories.
Is there any known solution for this? I even can't find anything helpful on Google.
Or, is there at least any other simple way to connect to multiple WireGuard VPN Servers from an Ubuntu 20.04 Client?
I have a VPS server running Ubuntu 18.04 LTS where I wanted to install a WireGuard VPN service. I have started with adding the repository and then installing the module which is running fine and without any error messages.
add-apt-repository ppa:wireguard/wireguard
apt-get update
apt-get install wireguard-dkms wireguard-tools
Then, I wanted to load the kernel module using
sudo modprobe wireguard
but, modprobe tells me, that it is unable to locate the kernel module.
modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file '/lib/modules/4.15.0/modules.builtin.bin'
modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.15.0
Rereading the console output, the installer told me that it had installed the module to /lib/modules/4.15.0-62-generic/updates/dkms, but modprobe seems to look only into /lib/modules/4.15.0/. I have already tried to create a symlink into the 4.15.0-directory, but modprobe still is not able to locate the module file.
The Ubuntu Server was 'out of box', since I was renewing it. Is anyone who can help?