From: Adrian Bunk <bunk@stusta.de>
To: Scott Ellis <scott@jumpnowtek.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-openembedded] Wireguard broken with 5.1+ kernels
Date: Tue, 14 May 2019 14:18:30 +0300 [thread overview]
Message-ID: <20190514111830.GC18877@localhost> (raw)
In-Reply-To: <41c04e88-4b89-6f1a-57a1-78bcbfcb562b@jumpnowtek.com>
On Tue, May 14, 2019 at 05:26:34AM -0400, Scott Ellis wrote:
> This kernel commit removes nf_nat_core.h which breaks wireguard 20190123.
>
> commit d2c5c103b1337f590b7edf1509a6e294bdf22402
> Author: Florian Westphal <fw@strlen.de>
> Date: Tue Feb 19 17:38:27 2019 +0100
>
> netfilter: nat: remove nf_nat_l3proto.h and nf_nat_core.h
>
>
> Version 20190406 of wireguard fixes this.
>
> Will a patch to upgrade the wireguard version on the warrior branch be
> accepted?
IMHO backporting the fix would be more appropriate for warrior.
And wireguard should be fixed or upgraded on master before this gets
fixed in warrior.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2019-05-14 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 9:26 [meta-openembedded] Wireguard broken with 5.1+ kernels Scott Ellis
2019-05-14 11:18 ` Adrian Bunk [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=20190514111830.GC18877@localhost \
--to=bunk@stusta.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=scott@jumpnowtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.