From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Wireguard is broken by recent ubuntu 18.04 kernel update
Date: Wed, 20 May 2020 15:21:31 +0200 [thread overview]
Message-ID: <f38d592b-3ea8-91ff-99d4-63ed4f2ba1e0@dd-wrt.com> (raw)
In-Reply-To: <e0484514-9c09-cc78-022c-54d0e59145cd@gmail.com>
current kernel update today broke wireguard-compat compile due a api
backport change. i'm sure it will be fixed soon by jason
Am 20.05.2020 um 15:14 schrieb Vasili Pupkin:
> The system is Ubuntu 18.04.4, and wireguard is broken in recent kernel
> update "5.3.0-53.47~18.04.1"... not sure why 18.04.1 is landed on
> 18.04.4 system
>
> # ip link add dev wg0 type wireguard
> Error: Unknown device type.
>
> And nothing is shown by "lsmod | grep wireguard' and "dmesg | grep
> wireguard"
>
> I've tried "apt install --reinstall wireguard" and "update-initramfs
> -u -k all" with no luck.
>
> Everything works fine with kernel 5.3.0-51
>
>
next prev parent reply other threads:[~2020-05-21 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 13:14 Wireguard is broken by recent ubuntu 18.04 kernel update Vasili Pupkin
2020-05-20 13:21 ` Sebastian Gottschall [this message]
2020-05-21 1:56 ` Jason A. Donenfeld
2020-05-21 1:51 ` Jason A. Donenfeld
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=f38d592b-3ea8-91ff-99d4-63ed4f2ba1e0@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--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).