Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Ada Sauce" <adasauce@with.parts>
To: wireguard@lists.zx2c4.com
Subject: Re: Ubuntu 18.04 kernel  4.15.0-106-generic breaks  wireguard-1.0.20200520
Date: Thu, 11 Jun 2020 15:41:47 -0300	[thread overview]
Message-ID: <44-5ee27b00-7-1574d920@168130139> (raw)
In-Reply-To: <44-5ee26e80-1-1574d920@168130073>

On Thursday, June 11, 2020 14:49 ADT, "Ada Sauce" <adasauce@with.parts> wrote:

> I'm now also observing the same failure mode as Martin.
>
> However, the kernel is 4.15.0-101-generic.
>
> ```
> /var/lib/dkms/wireguard/1.0.20200611/build/socket.c: In function ‘send6’:
> /var/lib/dkms/wireguard/1.0.20200611/build/socket.c:139:20: error: ‘const struct ipv6_stub’ has no member named ‘ipv6_dst_lookup_flow’; did you mean ‘ipv6_dst_lookup’?
>    dst = ipv6_stub->ipv6_dst_lookup_flow(sock_net(sock), sock, &fl,
>                     ^~~~~~~~~~~~~~~~~~~~
>                     ipv6_dst_lookup
> scripts/Makefile.build:330: recipe for target '/var/lib/dkms/wireguard/1.0.20200611/build/socket.o' failed
> make[1]: *** [/var/lib/dkms/wireguard/1.0.20200611/build/socket.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> Makefile:1577: recipe for target '_module_/var/lib/dkms/wireguard/1.0.20200611/build' failed
> make: *** [_module_/var/lib/dkms/wireguard/1.0.20200611/build] Error 2
> make: Leaving directory '/usr/src/linux-headers-4.15.0-101-generic'
> ```
>
> Cheers, Ada

Apologies for the spam, I finally got 4.15.0-106 via another apt-get update. It's working correctly with this kernel.

It looks like you were running the same kernel, Martin. Perhaps an update will fix it for you as well.

Cheers!


  reply	other threads:[~2020-06-17  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 17:49 Ada Sauce
2020-06-11 18:41 ` Ada Sauce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-11 12:16 Martin Jurasik
2020-06-10 10:41 Thilo-Alexander Ginkel
2020-06-10 15:34 ` YU News
2020-06-11  8:29 ` Jason A. Donenfeld
2020-06-11 12:05   ` Thilo-Alexander Ginkel

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=44-5ee27b00-7-1574d920@168130139 \
    --to=adasauce@with.parts \
    --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).