wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Laszlo KERTESZ <laszlo.kertesz@gmail.com>
To: Nils Cant <nils@krash.be>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard kernel module won't load on kernel 4.19.0-5 (Debian sid/buster)
Date: Sat, 22 Jun 2019 19:46:24 +0300	[thread overview]
Message-ID: <CANcuY=oBZ41KNEeKqqUP5J=5sR-GtffxGym74c2c7SfW=Xhr+g@mail.gmail.com> (raw)
In-Reply-To: <9bcc3e74ccde028b05ca66a3145da8bf@krash.be>


[-- Attachment #1.1: Type: text/plain, Size: 2134 bytes --]

I have this kernel on Debian Stretch (from backports) and wireguard works
just fine with it.


On Sat, Jun 22, 2019 at 10:52 AM Nils Cant <nils@krash.be> wrote:

> Hello,
>
> I'm unable to load the wireguard kernel module on Debian Sid or Debian
> Buster. (4.19.0-5-amd64 kernel)
> (Debian buster is scheduled to be promoted to stable in a couple of weeks)
>
> root@buster:~# modprobe wireguard
> modprobe: ERROR: could not insert 'wireguard': Invalid argument
> root@buster:~# modinfo wireguard
> filename: /lib/modules/4.19.0-5-amd64/updates/dkms/wireguard.ko
> alias: net-pf-16-proto-16-family-wireguard
> alias: rtnl-link-wireguard
> version: 0.0.20190601
> author: Jason A. Donenfeld <Jason@zx2c4.com>
> description: WireGuard secure network tunnel
> license: GPL v2
> srcversion: 69000E9D4B2B253E97C189A
> depends: udp_tunnel,ip6_udp_tunnel
> retpoline: Y
> name: wireguard
> vermagic: 4.19.0-5-amd64 SMP mod_unload modversions
>
> The same version seems to work fine on Debian Stretch (4.9.0-9) or Fedora
> Core 30 (5.1.11-300)
>
> The kernel ring throws a number of symbol version errors:
>
> [...]
> [ 97.450944] wireguard: loading out-of-tree module taints kernel.
> [ 97.453335] wireguard: module verification failed: signature and/or
> required key missing - tainting kernel
> [ 97.457727] wireguard: disagrees about version of symbol skb_put
> [ 97.459772] wireguard: Unknown symbol skb_put (err -22)
> [ 97.461555] wireguard: disagrees about version of symbol ip6_dst_hoplimit
> [ 97.463609] wireguard: Unknown symbol ip6_dst_hoplimit (err -22)
> [ 97.465590] wireguard: disagrees about version of symbol consume_skb
> [ 97.467495] wireguard: Unknown symbol consume_skb (err -22)
> [ 97.469326] wireguard: disagrees about version of symbol udp_sock_create4
> [...]
>
> I have tried both the apt package from debian unstable, as well as compile
> from source.
>
> Any idea what could be going wrong? Is this a Debian kernel bug?
>
>
> Thanks in advance,
>
> Nils
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

[-- Attachment #1.2: Type: text/html, Size: 2805 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      parent reply	other threads:[~2019-06-22 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 14:58 Wireguard kernel module won't load on kernel 4.19.0-5 (Debian sid/buster) Nils Cant
2019-06-22 12:23 ` Steven Honson
2019-06-22 16:46 ` Laszlo KERTESZ [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANcuY=oBZ41KNEeKqqUP5J=5sR-GtffxGym74c2c7SfW=Xhr+g@mail.gmail.com' \
    --to=laszlo.kertesz@gmail.com \
    --cc=nils@krash.be \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).