Skip to contentSkip to conversation

Wireguard is broken by recent ubuntu 18.04 kernel update

DISCUSSION Vasili Pupkin 3 participants 4 messages May 20, 2020 – May 21, 2020

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw

Hey Unit193,

Now would be a good time to bump the ppa for all the versions, as downstream finally released the new kernel.

Thanks,
Jason

Quoted 15 lines · 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

#2 lore raw
In reply to Vasili Pupkin

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:

Quoted 13 lines

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

#3 lore raw
Quoted 3 lines · Sebastian Gottschall

current kernel update today broke wireguard-compat compile due a api backport change. i'm sure it will be fixed soon by jason

It already is fixed. It's just a matter of the Ubuntu maintainer bumping the PPA.