Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Debian 10 Wireguard : Unable to access interface: Protocol not supported

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
leeuw
Posts: 5
Joined: 2021-08-17 14:35

Debian 10 Wireguard : Unable to access interface: Protocol not supported

#1 Post by leeuw »

Guys,


Could anyone help this modest linux user?

I try to install PiVPN on a VPS using this script:

curl -L https://install.pivpn.io | bash

I had to modify this script to pass the interface 'UP' problem. Since the interface 'venet0:' on my vps is 'UNKNOWN'
After that I locally ran the adaption and it finished fine.
In fact I think all configuration is allright except for the wg-quick service.
But Red lines appear when I list systemctl.

When I do : systemctl status wg-quick@wg0.service

it gives:

systemd[1]: Starting WireGuard via wg-quick(8) for wg0...
[#] ip link add wg0 type wireguard
: RTNETLINK answers: Operation not supported
: Unable to access interface: Protocol not supported
: [#] ip link delete dev wg0
: Cannot find device "wg0"
: wg-quick@wg0.service: Main process exited, code=exited, sta
: wg-quick@wg0.service: Failed with result 'exit-code'.
: Failed to start WireGuard via wg-quick(8) for wg0.


I know from other topics on this forum there are problems for wireguard with certain Debian versions.

My #uname -a output:

Linux 4.19.0 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64 GNU/Linux


~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster



On another local server with the same 4.19 kernel version it runs fine.
I am not sure where to trigger the problem. Has anyone experience with this error
and how to fix it? Please don't tell me to install another kernel. I have a lot of work
in the recent setup so far. :( Furthermore, I don't think my VPS provider has other Debian selections available...

Thanks in advance.

leeuw
Posts: 5
Joined: 2021-08-17 14:35

Re: Debian 10 Wireguard : Unable to access interface: Protocol not supported

#2 Post by leeuw »

I tried:

askubuntu.com/questions/1245454/wireguard-vpn-is-failing-with-error-cannot-find-device-wg0

and this:

askubuntu.com/questions/1306669/is-there-an-alternative-to-installing-all-kernel-headers-to-make-wireguard-run


But still when I reinstall wireguard dkms it reports during install that the right kernel header is not installed.
Weird.
Does nobody knows this issue?


update:

Module build for kernel 4.19.0 was skipped since the
kernel headers for this kernel does not seem to be installed.

wireguard.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-14-amd64/updates/dkms/

depmod...
modprobe: ERROR: missing parameters. See -h.


This is too far in the kernel guru stuff form me, I need help.

leeuw
Posts: 5
Joined: 2021-08-17 14:35

Re: Debian 10 Wireguard : Unable to access interface: Protocol not supported

#3 Post by leeuw »

No.


I am on the wrong track here. I installed the same pivpn script on a virtual Debian 10 server earlier.
Then, i didn't need to install kernel headers to get wireguard running.
So, what is it that the vps server doesn't like?

on this debian version it works:
Linux (virtualmachine) 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64 GNU/Linux

on this one it does not:
Linux (vps) 4.19.0 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64 GNU/Linux



Anyone?

ntn888
Posts: 9
Joined: 2021-09-05 01:35
Location: sydney
Has thanked: 2 times
Contact:

Re: Debian 10 Wireguard : Unable to access interface: Protocol not supported

#4 Post by ntn888 »

hi i'm not a pro user my self. are you trying to bring up a wireguard intreface? as i did it, it was just a couple of steps and worked on debian 10 & 11.

first edit the config file:
/etc/wireguard/wg0.conf

next run the command:
sudo wg-quick up wg0

hope it helps. sorry if i misunderstood ur problem...

Post Reply