RaxVentus's picture
RaxVentus - Wed, 2021/10/13 - 08:30

After setting it up, it can't make or find "wg0" and I cannot understand why.
I've tried reinstalling the DKMS modules for it, and it says they installed properly, but when I try to configure the server I get 

[#] ip link add wg0 type wireguard
Error: Unknown device type.
Unable to access interface: Protocol not supported
[#] ip link delete dev wg0
Cannot find device "wg0"

My proxmox container config is attached.

 

I have a feeling there's something glaringly obvious that I missed, but I cannot think of it.

 

Host is running: Linux 5.4.140-1-pve #1 SMP PVE 5.4.140-1 (Wed, 08 Sep 2021 16:21:59 +0200)

Container is running: Linux WireGuard 5.4.140-1-pve #1 SMP PVE 5.4.140-1 (Wed, 08 Sep 2021 16:21:59 +0200) x86_64

Template image downloaded is: debian-10-turnkey-wireguard_16.2.1_amd64
Forum: 
Support
Tags: 
wireguard
lxc proxmox
Jeremy Davis's picture

Jeremy Davis - Thu, 2021/10/14 - 23:42

Have you installed the DKMS module on the Proxmox host? AFAIK that is required when running Wireguard as a LXC guest (LXC leverages the host's kernel).

Once you've done that, then it should "just work" (may require host reboot?). However, if you still continue to have issues, please post the output of:

systemctl status wg-quick@wg0.service
badco's picture

badco - Fri, 2021/10/15 - 12:55

Wireguard should be baked in from kernel 6.x, so if they are using Proxmox 7 they should have it.

Jeremy Davis's picture

Jeremy Davis - Mon, 2021/10/18 - 01:23
Good point. Although we still don't know if it's loaded!? 
lsprobe | grep wireguard
badco's picture

badco - Fri, 2021/10/15 - 12:57

Alternatively, if running Proxmox 6.4 you can opt into kernel 5.11 :)

Jeremy Davis's picture

Jeremy Davis - Mon, 2021/10/18 - 01:31

The DKMS module is in (Debian buster) backports so can be installed via that path if required on an older kernel.

Add new comment