Wireguard container wg0 - Unknown device type - Protocol not supported

[driz]

I may be wrong, but I believe we found that the issue was with the 5.3 kernel… don’t quote me though, i can’t find the source right now.

[r0zzy5]

So is there a workaround that I can use to get this working?

[driz]

did you try upgrading (or downgrading) the kernel by any chance to get off the 5.3 train?

[TUISTERa]

This is my config, you need to download and compile wireguard-dkms in host to be ok`

  vpn:
    image: linuxserver/wireguard:latest
    container_name: vpn
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - SERVERURL=vpn.domain.com
      - SERVERPORT=53753
      - PEERS=5
      - PEERDNS=8.8.8.8
      - INTERNAL_SUBNET=192.168.20.0
    networks:
      - homelan
    volumes:
      - ${DOCKER_CONFIG}/wireguard/config:/config
      - /lib/modules:/lib/modules
    ports:
      - 51820:51820/udp
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
      - net.ipv4.ip_forward=1
    restart: unless-stopped

``

[aptalca]

We have a test build here that should prevent most kernel compile issues: lspipepr/wireguard:v1.0.20200513-pkg-9fe5b6c6-pr-39 It’s multi-arch

[r0zzy5]

@aptalca

lspipepr/wireguard

I don’t appear to be running the 5.3 kernel:

uname -a
Linux raspberrypi 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux

[aptalca]

just try it…

[driz]

@r0zzy5

having the same issue

@driz

get off the 5.3 train?

@r0zzy5

I don’t appear to be running the 5.3 kernel:

SAME issue?!?! obviously not though right? just try what aptalca told you and it will likely fix your issue (which is NOT the same)

[ByteBitten]

Took a while for me to update, but yes:
Update to kernel 5.4 fixed my issue.

[driz]

thanks for letting us know. That said, while we know there was an issue with 5.3 kernels, the lsiodev link aptalca provided can/should resolve the issue without a kernel upgrade from now on.

glad you got sorted though!