From: Bruno Wolff III <bruno@wolff.to>
To: wireguard@lists.zx2c4.com
Subject: [PATCH] net/netfilter/nf_nat_core.h was removed by d2c5c103b1337f590b7edf1509a6e294bdf22402
Date: Thu, 14 Mar 2019 13:25:34 -0500 [thread overview]
Message-ID: <20190314182534.23660-1-bruno@wolff.to> (raw)
It looks like net/netfilter/nf_nat_core.h isn't needed any more and things
seemed to work without it.
Signed-off-by: Bruno Wolff III <bruno@wolff.to>
---
src/compat/compat.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/compat/compat.h b/src/compat/compat.h
index 7a61e4c1a5cd..2dcdbaeb0ad6 100644
--- a/src/compat/compat.h
+++ b/src/compat/compat.h
@@ -792,7 +792,9 @@ struct __kernel_timespec {
#include <net/ipv6.h>
#include <net/icmp.h>
#include <net/netfilter/nf_conntrack.h>
+#if LINUX_VERSION_CODE < KERNEL_VERSION(5, 1, 0)
#include <net/netfilter/nf_nat_core.h>
+#endif
static inline void new_icmp_send(struct sk_buff *skb_in, int type, int code, __be32 info)
{
enum ip_conntrack_info ctinfo;
--
2.21.0
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-03-14 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 18:25 Bruno Wolff III [this message]
2019-03-14 18:52 ` [PATCH] net/netfilter/nf_nat_core.h was removed by d2c5c103b1337f590b7edf1509a6e294bdf22402 Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2019-03-14 5:32 Bruno Wolff III
2019-03-14 5:24 Bruno Wolff III
2019-03-14 5:21 Bruno Wolff III
2019-03-14 5:34 ` Bruno Wolff III
2019-03-14 7:10 ` Aleksa Sarai
2019-03-14 12:41 ` Bruno Wolff III
2019-03-14 13:24 ` Luis Ressel
2019-03-14 5:14 Bruno Wolff III
2019-03-14 17:05 ` Bruno Wolff III
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=20190314182534.23660-1-bruno@wolff.to \
--to=bruno@wolff.to \
--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).