Skip to content
This repository has been archived by the owner on Apr 17, 2024. It is now read-only.

Wireguard doesn't work #315

Open
c25 opened this issue Aug 19, 2022 · 1 comment
Open

Wireguard doesn't work #315

c25 opened this issue Aug 19, 2022 · 1 comment

Comments

@c25
Copy link
Contributor

c25 commented Aug 19, 2022

This is probably due to kernel headers being missing/mismatched.

  • Install wireguard via apt (this is tested on debian unstable)
  • configure your connection
  • run wg-quick up wg0
  • receive the following error(s)
Error: Unknown device type.
Unable to access interface: Protocol not supported

This appears to be because we're lacking the wireguard kernel module.

installing wireguard-dkms (or running dpkg-reconfigure wireguard-dkms) fails/skips as the kernel headers for the running kernel are not installed.

$uname -r
5.10.106

linux-headers-amd64 5.18.16-1 are installed

Even if we could install the correct version I doubt they would match the running (chromebook) kernel.

@jkaplavka
Copy link

Yes it's custom kernel modified by google so mainline headers doesn't work, but since kernel 5.6 there is a wireguard module build in. I'm on kernel 5.15 with working wireguard. Try this sudo modprobe wireguard if that doesn't work you will have to change kernel config and rebuild kernel with wireguard module https://cb-linux.github.io/breath/docs.html#/kernel?id=new-build-script, this config needs to be enabled https://www.kernelconfig.io/search?q=CONFIG_WIREGUARD&kernelversion=5.10.137&arch=x86

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants