netfilter: nft_ct: add ct expectations support
Subsystems (2)
PATCH 1/1 netfilter: nft_ct: add ct expectations support
This patch allows to add, list and delete expectations via nft objref infrastructure and assigning these expectations via nft rule.
--- include/uapi/linux/netfilter/nf_tables.h | 15 ++- net/netfilter/nft_ct.c | 124 ++++++++++++++++++++++- 2 files changed, 136 insertions(+), 3 deletions(-)
include/uapi/linux/netfilter/nf_tables.h +14 -1
@@ -968,6 +968,7 @@ enum nft_socket_keys {* @NFT_CT_DST_IP6: conntrack layer 3 protocol destination (IPv6 address) * @NFT_CT_TIMEOUT: connection tracking timeout policy assigned to conntrack * @NFT_CT_ID: conntrack id +* @NFT_CT_EXPECT: connection tracking expectation */ enum nft_ct_keys {NFT_CT_STATE ,
@@ -995,6 +996,7 @@ enum nft_ct_keys {NFT_CT_DST_IP6 ,NFT_CT_TIMEOUT ,NFT_CT_ID , +NFT_CT_EXPECT , __NFT_CT_MAX };#define NFT_CT_MAX (__NFT_CT_MAX - 1)
@@ -1447,6 +1449,16 @@ enum nft_ct_timeout_timeout_attributes { };#define NFTA_CT_TIMEOUT_MAX (__NFTA_CT_TIMEOUT_MAX - 1) +enum nft_ct_expectation_attributes { +NFTA_CT_EXPECT_UNSPEC , +NFTA_CT_EXPECT_L3PROTO , +NFTA_CT_EXPECT_L4PROTO , +NFTA_CT_EXPECT_DPORT , +NFTA_CT_EXPECT_TIMEOUT , + __NFTA_CT_EXPECT_MAX, +}; +#define NFTA_CT_EXPECT_MAX (__NFTA_CT_EXPECT_MAX - 1) +#define NFT_OBJECT_UNSPEC 0#define NFT_OBJECT_COUNTER 1#define NFT_OBJECT_QUOTA 2
@@ -1456,7 +1468,8 @@ enum nft_ct_timeout_timeout_attributes {#define NFT_OBJECT_TUNNEL 6#define NFT_OBJECT_CT_TIMEOUT 7#define NFT_OBJECT_SECMARK 8 -#define __NFT_OBJECT_MAX 9 +#define NFT_OBJECT_CT_EXPECT 9 +#define __NFT_OBJECT_MAX 10#define NFT_OBJECT_MAX (__NFT_OBJECT_MAX - 1)/**
net/netfilter/nft_ct.c +122 -2
160 lines not on this page · raw message
Signature · 1 line
2.21.0
Florian Westphal
maintainerQuoted 15 lines · Stéphane Veyret
net/netfilter/nft_ct.c +15
-0+static void nft_ct_expect_obj_eval (struct nft_object *obj, +struct nft_regs *regs, +const struct nft_pktinfo *pkt) +{ +const struct nft_ct_expect_obj *priv =nft_obj_data (obj); +enum ip_conntrack_info ctinfo; +struct nf_conn *ct =nf_ct_get (pkt->skb, ctinfo); +int dir =CTINFO2DIR (ctinfo); +struct nf_conntrack_expect *exp; + + exp =nf_ct_expect_alloc (ct); +if (exp ==NULL ) { +nf_ct_helper_log (skb, ct,"cannot allocate expectation" ); + regs->verdict.code =NF_DROP ; +return ;
net/netfilter/nft_ct.c static struct nft_expr_type nft_notrack_type __read_mostly = { · line 874
Quoted 10 lines
net/netfilter/nft_ct.c +10
-0+ } + +nf_ct_expect_init (exp,NF_CT_EXPECT_CLASS_DEFAULT , priv->l3num, + &ct->tuplehash[!dir].tuple.src.u3, &ct->tuplehash[!dir].tuple.dst.u3, + priv->l4proto,NULL , &priv->dport); +if (priv->timeout) + exp->timeout.expires = jiffies + priv->timeout *HZ ; + +if (nf_ct_expect_related (exp) !=0 ) { +nf_ct_helper_log (skb, ct,"cannot add expectation" );
Please remove the nf_ct_helper_log() calls, it will crash in case there is no helper attached to the conntrack.
Other than this I don't see any issues here, thanks for working on this!
Pablo Neira Ayuso
maintainerQuoted 2 lines · Stéphane Veyret
This patch allows to add, list and delete expectations via nft objref infrastructure and assigning these expectations via nft rule.
Please, add to your patch title your patch version, ie.
[PATCH nf-next,v2] nft_ct: add ct expectations support
Could you describe the usecase example for this infrastructure, please?
More comments below.
Quoted 19 lines
Signed-off-by Stéphane Veyret <[email protected]>--- include/uapi/linux/netfilter/nf_tables.h | 15 ++- net/netfilter/nft_ct.c | 124 ++++++++++++++++++++++- 2 files changed, 136 insertions(+), 3 deletions(-)include/uapi/linux/netfilter/nf_tables.h +1
-0@@ -968,6 +968,7 @@ enum nft_socket_keys {* @NFT_CT_DST_IP6: conntrack layer 3 protocol destination (IPv6 address) * @NFT_CT_TIMEOUT: connection tracking timeout policy assigned to conntrack * @NFT_CT_ID: conntrack id +* @NFT_CT_EXPECT: connection tracking expectation */ enum nft_ct_keys {NFT_CT_STATE ,
include/uapi/linux/netfilter/nf_tables.h enum nft_ct_keys { · line 999
Quoted 4 lines
include/uapi/linux/netfilter/nf_tables.h +1
-0@@ -995,6 +996,7 @@ enum nft_ct_keys {NFT_CT_DST_IP6 ,NFT_CT_TIMEOUT ,NFT_CT_ID , + NFT_CT_EXPECT,
You don't this definition, or I don't find where this is used.
Quoted 60 lines
include/uapi/linux/netfilter/nf_tables.h +12
-1__NFT_CT_MAX };#define NFT_CT_MAX (__NFT_CT_MAX - 1)@@ -1447,6 +1449,16 @@ enum nft_ct_timeout_timeout_attributes { };#define NFTA_CT_TIMEOUT_MAX (__NFTA_CT_TIMEOUT_MAX - 1) +enum nft_ct_expectation_attributes { +NFTA_CT_EXPECT_UNSPEC , +NFTA_CT_EXPECT_L3PROTO , +NFTA_CT_EXPECT_L4PROTO , +NFTA_CT_EXPECT_DPORT , +NFTA_CT_EXPECT_TIMEOUT , + __NFTA_CT_EXPECT_MAX, +}; +#define NFTA_CT_EXPECT_MAX (__NFTA_CT_EXPECT_MAX - 1) +#define NFT_OBJECT_UNSPEC 0#define NFT_OBJECT_COUNTER 1#define NFT_OBJECT_QUOTA 2@@ -1456,7 +1468,8 @@ enum nft_ct_timeout_timeout_attributes {#define NFT_OBJECT_TUNNEL 6#define NFT_OBJECT_CT_TIMEOUT 7#define NFT_OBJECT_SECMARK 8 -#define __NFT_OBJECT_MAX 9 +#define NFT_OBJECT_CT_EXPECT 9 +#define __NFT_OBJECT_MAX 10#define NFT_OBJECT_MAX (__NFT_OBJECT_MAX - 1)/** net/netfilter/nft_ct.c +15
-0@@ -24,6 +24,7 @@#include <net/netfilter/nf_conntrack_labels.h> #include <net/netfilter/nf_conntrack_timeout.h> #include <net/netfilter/nf_conntrack_l4proto.h> +#include <net/netfilter/nf_conntrack_expect.h> struct nft_ct {enum nft_ct_keys key:8 ;@@ -790,6 +791,117 @@ static struct nft_expr_type nft_notrack_type __read_mostly = { .owner = THIS_MODULE, }; +struct nft_ct_expect_obj { +int l3num; +u8 l4proto; +__be16 dport; +u32 timeout; +}; + +static int nft_ct_expect_obj_init (const struct nft_ctx *ctx, +const struct nlattr *const tb[], +struct nft_object *obj) +{ +struct nft_ct_expect_obj *priv =nft_obj_data (obj); +int ret; +
net/netfilter/nft_ct.c static struct nft_expr_type nft_notrack_type __read_mostly = { · line 817
Quoted 10 lines
net/netfilter/nft_ct.c +10
-0+if (!tb[NFTA_CT_EXPECT_L4PROTO ] || + !tb[NFTA_CT_EXPECT_DPORT ]) +return -EINVAL ; + + priv->l3num = ctx->family; +if (tb[NFTA_CT_EXPECT_L3PROTO ]) + priv->l3num =ntohs (nla_get_be16 (tb[NFTA_CT_EXPECT_L3PROTO ])); + priv->l4proto =nla_get_u8 (tb[NFTA_CT_EXPECT_L4PROTO ]); + + priv->dportmin =nla_get_be16 (tb[NFTA_CT_EXPECT_DPORT_MIN ]);
Where is NFTA_CT_EXPECT_DPORT_MIN defined? You don't check for this attribute, it may not be present. Looks like a leftover?
Quoted 18 lines
net/netfilter/nft_ct.c +18
-0+ + priv->timeout =0 ; +if (tb[NFTA_CT_EXPECT_TIMEOUT ]) + priv->timeout =nla_get_u32 (tb[NFTA_CT_EXPECT_TIMEOUT ]); + + ret =nf_ct_netns_get (ctx->net, ctx->family); +if (ret <0 ) +return ret; + +return 0 ; +} + +static void nft_ct_expect_obj_destroy (const struct nft_ctx *ctx, +struct nft_object *obj) +{ +nf_ct_netns_put (ctx->net, ctx->family); +} +
net/netfilter/nft_ct.c static struct nft_expr_type nft_notrack_type __read_mostly = { · line 845
Quoted 10 lines
net/netfilter/nft_ct.c +10
-0+static int nft_ct_expect_obj_dump (struct sk_buff *skb, +struct nft_object *obj,bool reset) +{ +const struct nft_ct_expect_obj *priv =nft_obj_data (obj); + +if (nla_put_be16 (skb,NFTA_CT_EXPECT_L3PROTO ,htons (priv->l3num)) || +nla_put_u8 (skb,NFTA_CT_EXPECT_L4PROTO , priv->l4proto) || +nla_put_be16 (skb,NFTA_CT_EXPECT_DPORT , priv->dport) || +nla_put_u32 (skb,NFTA_CT_EXPECT_TIMEOUT , priv->timeout)) +return -1
This won't compile, missing ';'. Also indentation.
Quoted 14 lines
net/netfilter/nft_ct.c +14
-0+ +return 0 ; +} + +static void nft_ct_expect_obj_eval (struct nft_object *obj, +struct nft_regs *regs, +const struct nft_pktinfo *pkt) +{ +const struct nft_ct_expect_obj *priv =nft_obj_data (obj); +enum ip_conntrack_info ctinfo; +struct nf_conn *ct =nf_ct_get (pkt->skb, ctinfo); +int dir =CTINFO2DIR (ctinfo); +struct nf_conntrack_expect *exp; +
net/netfilter/nft_ct.c static struct nft_expr_type nft_notrack_type __read_mostly = { · line 869
Quoted 10 lines
net/netfilter/nft_ct.c +10
-0+ exp =nf_ct_expect_alloc (ct); +if (exp ==NULL ) { +nf_ct_helper_log (skb, ct,"cannot allocate expectation" ); + regs->verdict.code =NF_DROP ; +return ; + } + +nf_ct_expect_init (exp,NF_CT_EXPECT_CLASS_DEFAULT , priv->l3num, + &ct->tuplehash[!dir].tuple.src.u3, &ct->tuplehash[!dir].tuple.dst.u3, + priv->l4proto,NULL , &priv->dport);
Coding style:
nf_ct_expect_init(exp, NF_CT_EXPECT_CLASS_DEFAULT, priv->l3num,
&ct->tuplehash[!dir].tuple.src.u3,
&ct->tuplehash[!dir].tuple.dst.u3,
priv->l4proto, NULL, &priv->dport);net/netfilter/nft_ct.c static struct nft_expr_type nft_notrack_type __read_mostly = { · line 871
Quoted 2 lines
net/netfilter/nft_ct.c +2
-0+if (priv->timeout) + exp->timeout.expires = jiffies + priv->timeout *HZ ;
timeout should be made mandatory? why check if it's set?
net/netfilter/nft_ct.c static struct nft_expr_type nft_notrack_type __read_mostly = { · line 883
Quoted 11 lines
net/netfilter/nft_ct.c +11
-0+if (nf_ct_expect_related (exp) !=0 ) { +nf_ct_helper_log (skb, ct,"cannot add expectation" ); + regs->verdict.code =NF_DROP ; + } +} + +static const struct nla_policy nft_ct_expect_policy[NFTA_CT_EXPECT_MAX +1 ] = { + [NFTA_CT_EXPECT_L3PROTO ] = {.type =NLA_U16 }, + [NFTA_CT_EXPECT_L4PROTO ] = {.type =NLA_U8 }, + [NFTA_CT_EXPECT_DPORT ] = {.type =NLA_U16 }, + [NFTA_CT_EXPECT_TIMEOUT ] = {.type =NLA_U32 },
I'd prefer:
[NFTA_CT_EXPECT_L3PROTO] = { .type = NLA_U16 },
[NFTA_CT_EXPECT_L4PROTO] = { .type = NLA_U8 },
[NFTA_CT_EXPECT_DPORT] = { .type = NLA_U16 },
[NFTA_CT_EXPECT_TIMEOUT] = { .type = NLA_U32 },Thanks!
PATCH v2 1/1 netfilter: nft_ct: add ct expectations support
This patch allows to add, list and delete expectations via nft objref infrastructure and assigning these expectations via nft rule.
This allows manual port triggering when no helper is defined to manage a specific protocol. For example, if I have an online game which protocol is based on initial connection to TCP port 9753 of the server, and where the server opens a connection to port 9876, I can set rules as follow:
table ip filter {
ct expectation mygame {
protocol udp;
dport 9876;
}
chain input {
type filter hook input priority 0; policy drop;
tcp dport 9753 ct expectation set "mygame";
}
chain output {
type filter hook output priority 0; policy drop;
udp dport 9876 ct status expected accept;
}
}--- include/uapi/linux/netfilter/nf_tables.h | 13 ++- net/netfilter/nft_ct.c | 124 ++++++++++++++++++++++- 2 files changed, 134 insertions(+), 3 deletions(-)
include/uapi/linux/netfilter/nf_tables.h +12 -1
@@ -1447,6 +1447,16 @@ enum nft_ct_timeout_timeout_attributes { };#define NFTA_CT_TIMEOUT_MAX (__NFTA_CT_TIMEOUT_MAX - 1) +enum nft_ct_expectation_attributes { +NFTA_CT_EXPECT_UNSPEC , +NFTA_CT_EXPECT_L3PROTO , +NFTA_CT_EXPECT_L4PROTO , +NFTA_CT_EXPECT_DPORT , +NFTA_CT_EXPECT_TIMEOUT , + __NFTA_CT_EXPECT_MAX, +}; +#define NFTA_CT_EXPECT_MAX (__NFTA_CT_EXPECT_MAX - 1) +#define NFT_OBJECT_UNSPEC 0#define NFT_OBJECT_COUNTER 1#define NFT_OBJECT_QUOTA 2
@@ -1456,7 +1466,8 @@ enum nft_ct_timeout_timeout_attributes {#define NFT_OBJECT_TUNNEL 6#define NFT_OBJECT_CT_TIMEOUT 7#define NFT_OBJECT_SECMARK 8 -#define __NFT_OBJECT_MAX 9 +#define NFT_OBJECT_CT_EXPECT 9 +#define __NFT_OBJECT_MAX 10#define NFT_OBJECT_MAX (__NFT_OBJECT_MAX - 1)/**
net/netfilter/nft_ct.c +122 -2
160 lines not on this page · raw message
Signature · 1 line
2.21.0
Hi Pablo,
Quoted 5 lines · Pablo Neira Ayuso
Quoted 3 lines
NFT_CT_TIMEOUT, NFT_CT_ID,+
NFT_CT_EXPECT,You don't this definition, or I don't find where this is used.
As I told previously, I just copied the way timeout is built, and therefore, it seems that NFT_CT_TIMEOUT is not used too. But I actually saw today that these values are used in the « nftables » project. There is a copy of nf_tables.h there. Not sure it is a good idea to keep the variables in « nftables » and not in kernel.
Pablo Neira Ayuso
maintainerQuoted 7 lines · Stéphane Veyret
Hi Pablo,
Quoted 4 lines · Pablo Neira Ayuso
Quoted 3 lines
NFT_CT_TIMEOUT, NFT_CT_ID,+
NFT_CT_EXPECT,
Quoted 7 lines
Quoted 1 line
You don't this definition, or I don't find where this is used.
As I told previously, I just copied the way timeout is built, and therefore, it seems that
NFT_CT_TIMEOUTis not used too. But I actually saw today that these values are used in the « nftables » project. There is a copy ofnf_tables.hthere. Not sure it is a good idea to keep the variables in « nftables » and not in kernel.
I have just updated the cached copy of nf_tables.h in git.netfilter.org:
http://git.netfilter.org/nftables/commit/?id=d3869cae9d6232b9f3fa720e5516ece95fdbe73e
Thanks.
Quoted 7 lines · Pablo Neira Ayuso
Quoted 4 lines
But I actually saw today that these values are used in the « nftables » project. There is a copy of
nf_tables.hthere. Not sure it is a good idea to keep the variables in « nftables » and not in kernel.I have just updated the cached copy of
nf_tables.hin git.netfilter.org:
So now nftables does not compile anymore, does it? What do you think we should do, then? Add a new variable, out of nf_tables.h, in nftables project?
Pablo Neira Ayuso
maintainerQuoted 6 lines · Stéphane Veyret
Quoted 5 lines · Pablo Neira Ayuso
Quoted 4 lines
But I actually saw today that these values are used in the « nftables » project. There is a copy of
nf_tables.hthere. Not sure it is a good idea to keep the variables in « nftables » and not in kernel.
Quoted 6 lines
Quoted 2 lines
I have just updated the cached copy of
nf_tables.hin git.netfilter.org:So now nftables does not compile anymore, does it? What do you think we should do, then? Add a new variable, out of
nf_tables.h, in nftables project?
Please, do not add a new enumeration definition to nf_tables.h for something we do not need in UAPI.
Thanks.