Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: [PATCH 08/11] netfilter: nft_flow_offload: set liberal tracking mode for tcp
Date: Thu, 23 May 2019 23:35:44 +0200	[thread overview]
Message-ID: <20190523213547.15523-9-pablo@netfilter.org> (raw)
In-Reply-To: <20190523213547.15523-1-pablo@netfilter.org>

From: Florian Westphal <fw@strlen.de>

Without it, whenever a packet has to be pushed up the stack (e.g. because
of mtu mismatch), then conntrack will flag packets as invalid, which in
turn breaks NAT.

Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---
 net/netfilter/nft_flow_offload.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/net/netfilter/nft_flow_offload.c b/net/netfilter/nft_flow_offload.c
index 69d7a8439c7a..bde63d9c3c4e 100644
--- a/net/netfilter/nft_flow_offload.c
+++ b/net/netfilter/nft_flow_offload.c
@@ -72,6 +72,7 @@ static void nft_flow_offload_eval(const struct nft_expr *expr,
 	struct nf_flow_route route;
 	struct flow_offload *flow;
 	enum ip_conntrack_dir dir;
+	bool is_tcp = false;
 	struct nf_conn *ct;
 	int ret;
 
@@ -84,6 +85,8 @@ static void nft_flow_offload_eval(const struct nft_expr *expr,
 
 	switch (ct->tuplehash[IP_CT_DIR_ORIGINAL].tuple.dst.protonum) {
 	case IPPROTO_TCP:
+		is_tcp = true;
+		break;
 	case IPPROTO_UDP:
 		break;
 	default:
@@ -108,6 +111,11 @@ static void nft_flow_offload_eval(const struct nft_expr *expr,
 	if (!flow)
 		goto err_flow_alloc;
 
+	if (is_tcp) {
+		ct->proto.tcp.seen[0].flags |= IP_CT_TCP_FLAG_BE_LIBERAL;
+		ct->proto.tcp.seen[1].flags |= IP_CT_TCP_FLAG_BE_LIBERAL;
+	}
+
 	ret = flow_offload_add(flowtable, flow);
 	if (ret < 0)
 		goto err_flow_add;
-- 
2.11.0


  parent reply	other threads:[~2019-05-23 21:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 21:35 [PATCH 00/11] Netfilter/IPVS fixes for net Pablo Neira Ayuso
2019-05-23 21:35 ` [PATCH 01/11] netfilter: nf_tables: fix oops during rule dump Pablo Neira Ayuso
2019-05-23 21:35 ` [PATCH 02/11] netfilter: nf_queue: fix reinject verdict handling Pablo Neira Ayuso
2019-05-23 21:35 ` [PATCH 03/11] netfilter: nft_fib: Fix existence check support Pablo Neira Ayuso
2019-05-23 21:35 ` [PATCH 04/11] ipvs: Fix use-after-free in ip_vs_in Pablo Neira Ayuso
2019-05-23 21:35 ` [PATCH 05/11] selftests: netfilter: missing error check when setting up veth interface Pablo Neira Ayuso
2019-05-23 21:35 ` [PATCH 06/11] netfilter: nat: fix udp checksum corruption Pablo Neira Ayuso
2019-05-23 21:35 ` [PATCH 07/11] netfilter: nf_flow_table: ignore DF bit setting Pablo Neira Ayuso
2019-05-23 21:35 ` Pablo Neira Ayuso [this message]
2019-05-23 21:35 ` [PATCH 09/11] netfilter: nft_flow_offload: don't offload when sequence numbers need adjustment Pablo Neira Ayuso
2019-05-23 21:35 ` [PATCH 10/11] netfilter: nft_flow_offload: IPCB is only valid for ipv4 family Pablo Neira Ayuso
2019-05-23 21:35 ` [PATCH 11/11] selftests: netfilter: add flowtable test script Pablo Neira Ayuso
2019-05-23 21:45 ` [PATCH 00/11] Netfilter/IPVS fixes for net David Miller

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=20190523213547.15523-9-pablo@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    /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