@@ -536,6 +536,7 @@ enum nft_exthdr_attributes {
* @NFT_META_BRI_IIFNAME: packet input bridge interface name
* @NFT_META_BRI_OIFNAME: packet output bridge interface name
* @NFT_META_PKTTYPE: packet type
+ * @NFT_META_CPU: packet cpu
*/
enum nft_meta_keys {
NFT_META_LEN,
@@ -558,6 +559,7 @@ enum nft_meta_keys {
NFT_META_BRI_IIFNAME,
NFT_META_BRI_OIFNAME,
NFT_META_PKTTYPE,
+ NFT_META_CPU,
};
/**
@@ -393,6 +393,9 @@ static const struct meta_template meta_templates[] = {
[NFT_META_PKTTYPE] = META_TEMPLATE("pkttype", &pkttype_type,
BITS_PER_BYTE,
BYTEORDER_HOST_ENDIAN),
+ [NFT_META_CPU] = META_TEMPLATE("cpu", &integer_type,
+ BITS_PER_BYTE,
+ BYTEORDER_HOST_ENDIAN),
};
static void meta_expr_print(const struct expr *expr)
@@ -325,6 +325,7 @@ static int monitor_lookup_event(const char *event)
%token IBRIPORT "ibriport"
%token OBRIPORT "obriport"
%token PKTTYPE "pkttype"
+%token CPU "cpu"
%token CT "ct"
%token DIRECTION "direction"
@@ -1786,6 +1787,7 @@ meta_key_unqualified : MARK { $$ = NFT_META_MARK; }
| IBRIPORT { $$ = NFT_META_BRI_IIFNAME; }
| OBRIPORT { $$ = NFT_META_BRI_OIFNAME; }
| PKTTYPE { $$ = NFT_META_PKTTYPE; }
+ | CPU { $$ = NFT_META_CPU; }
;
meta_stmt : META meta_key SET expr
@@ -407,6 +407,7 @@ addrstring ({macaddr}|{ip4addr}|{ip6addr})
"ibriport" { return IBRIPORT; }
"obriport" { return OBRIPORT; }
"pkttype" { return PKTTYPE; }
+"cpu" { return CPU; }
"ct" { return CT; }
"direction" { return DIRECTION; }
This allows you to match cpu handling with a packet. This is an example of the syntax for this new attribute: nft add rule ip test input meta cpu 1 counter nft add rule ip test input meta cpu 1-3 counter nft add rule ip test input meta cpu { 1, 3} counter Signed-off-by: Ana Rey <anarey@gmail.com> --- include/linux/netfilter/nf_tables.h | 2 ++ src/meta.c | 3 +++ src/parser.y | 2 ++ src/scanner.l | 1 + 4 files changed, 8 insertions(+)