From: Ana Rey <anarey@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Ana Rey <anarey@gmail.com>, Alvaro Neira Ayuso <alvaroneay@gmail.com>
Subject: [nft PATCH v2] src: Add support for pkttype in meta expresion
Date: Tue, 5 Aug 2014 20:33:39 +0200 [thread overview]
Message-ID: <1407263619-4573-1-git-send-email-anarey@gmail.com> (raw)
In-Reply-To: <53df650e.e335c20a.2c4f.4d82@mx.google.com>
If It wants to declare a pktype attribute, It has used a syntax like this:
nft add rule ip filter input meta pkttype broadcast
Joint work with Alvaro Neira Ayuso <alvaroneay@gmail.com>
Signed-off-by: Alvaro Neira Ayuso <alvaroneay@gmail.com>
Signed-off-by: Ana Rey <anarey@gmail.com>
---
[Changes in v2:]
* Fix the description of @TYPE_PKTTYPE datatype and @NFT_META_PKTTYPE
attribute.
* Delete "loopback" symbol of pkttype_type_tbl table of symbol.
* Add SYMBOL_LIST_END in pkttype_type_tbl table of symbol to avoid
incorrect option of pkttype.
include/datatype.h | 2 ++
include/linux/netfilter/nf_tables.h | 2 ++
src/meta.c | 55 +++++++++++++++++++++++++++++++++++
src/parser.y | 2 ++
src/scanner.l | 1 +
5 files changed, 62 insertions(+)
diff --git a/include/datatype.h b/include/datatype.h
index 2c66e9d..5182263 100644
--- a/include/datatype.h
+++ b/include/datatype.h
@@ -35,6 +35,7 @@
* @TYPE_CT_STATUS: conntrack status (bitmask subtype)
* @TYPE_ICMP6_TYPE: ICMPv6 type codes (integer subtype)
* @TYPE_CT_LABEL: Conntrack Label (bitmask subtype)
+ * @TYPE_PKTTYPE: packet type (integer subtype)
*/
enum datatypes {
TYPE_INVALID,
@@ -68,6 +69,7 @@ enum datatypes {
TYPE_CT_STATUS,
TYPE_ICMP6_TYPE,
TYPE_CT_LABEL,
+ TYPE_PKTTYPE,
__TYPE_MAX
};
#define TYPE_MAX (__TYPE_MAX - 1)
diff --git a/include/linux/netfilter/nf_tables.h b/include/linux/netfilter/nf_tables.h
index a5f8ec0..fbc7904 100644
--- a/include/linux/netfilter/nf_tables.h
+++ b/include/linux/netfilter/nf_tables.h
@@ -535,6 +535,7 @@ enum nft_exthdr_attributes {
* @NFT_META_L4PROTO: layer 4 protocol number
* @NFT_META_BRI_IIFNAME: packet input bridge interface name
* @NFT_META_BRI_OIFNAME: packet output bridge interface name
+ * @NFT_META_PKTTYPE: packet type
*/
enum nft_meta_keys {
NFT_META_LEN,
@@ -556,6 +557,7 @@ enum nft_meta_keys {
NFT_META_L4PROTO,
NFT_META_BRI_IIFNAME,
NFT_META_BRI_OIFNAME,
+ NFT_META_PKTTYPE,
};
/**
diff --git a/src/meta.c b/src/meta.c
index 80f88ff..2c61455 100644
--- a/src/meta.c
+++ b/src/meta.c
@@ -20,6 +20,7 @@
#include <pwd.h>
#include <grp.h>
#include <linux/pkt_sched.h>
+#include <linux/if_packet.h>
#include <nftables.h>
#include <expression.h>
@@ -297,6 +298,57 @@ static const struct datatype gid_type = {
.parse = gid_type_parse,
};
+static const struct symbol_table pkttype_type_tbl = {
+ .symbols = {
+ SYMBOL("unicast", PACKET_HOST),
+ SYMBOL("broadcast", PACKET_BROADCAST),
+ SYMBOL("multicast", PACKET_MULTICAST),
+ SYMBOL_LIST_END,
+ },
+};
+
+static void pkttype_type_print(const struct expr *expr)
+{
+ return symbolic_constant_print(&pkttype_type_tbl, expr);
+}
+
+static struct error_record *pkttype_type_parse(const struct expr *sym,
+ struct expr **res)
+{
+ struct error_record *erec;
+ const struct symbolic_constant *s;
+
+ for (s = pkttype_type_tbl.symbols; s->identifier != NULL; s++) {
+ if (!strcmp(sym->identifier, s->identifier)) {
+ *res = constant_expr_alloc(&sym->location, sym->dtype,
+ sym->dtype->byteorder,
+ sym->dtype->size,
+ &s->value);
+ return NULL;
+ }
+ }
+
+ *res = NULL;
+ erec = sym->dtype->basetype->parse(sym, res);
+ if (erec != NULL)
+ return erec;
+ if (*res)
+ return NULL;
+
+ return symbolic_constant_parse(sym, &pkttype_type_tbl, res);
+}
+
+static const struct datatype pkttype_type = {
+ .type = TYPE_PKTTYPE,
+ .name = "pkttype",
+ .desc = "Packet type",
+ .byteorder = BYTEORDER_HOST_ENDIAN,
+ .size = BITS_PER_BYTE,
+ .basetype = &integer_type,
+ .print = pkttype_type_print,
+ .parse = pkttype_type_parse,
+};
+
static const struct meta_template meta_templates[] = {
[NFT_META_LEN] = META_TEMPLATE("length", &integer_type,
4 * 8, BYTEORDER_HOST_ENDIAN),
@@ -338,6 +390,9 @@ static const struct meta_template meta_templates[] = {
[NFT_META_BRI_OIFNAME] = META_TEMPLATE("obriport", &string_type,
IFNAMSIZ * BITS_PER_BYTE,
BYTEORDER_HOST_ENDIAN),
+ [NFT_META_PKTTYPE] = META_TEMPLATE("pkttype", &pkttype_type,
+ BITS_PER_BYTE,
+ BYTEORDER_HOST_ENDIAN),
};
static void meta_expr_print(const struct expr *expr)
diff --git a/src/parser.y b/src/parser.y
index 3e08e21..6da6e98 100644
--- a/src/parser.y
+++ b/src/parser.y
@@ -324,6 +324,7 @@ static int monitor_lookup_event(const char *event)
%token RTCLASSID "rtclassid"
%token IBRIPORT "ibriport"
%token OBRIPORT "obriport"
+%token PKTTYPE "pkttype"
%token CT "ct"
%token DIRECTION "direction"
@@ -1784,6 +1785,7 @@ meta_key_unqualified : MARK { $$ = NFT_META_MARK; }
| RTCLASSID { $$ = NFT_META_RTCLASSID; }
| IBRIPORT { $$ = NFT_META_BRI_IIFNAME; }
| OBRIPORT { $$ = NFT_META_BRI_OIFNAME; }
+ | PKTTYPE { $$ = NFT_META_PKTTYPE; }
;
meta_stmt : META meta_key SET expr
diff --git a/src/scanner.l b/src/scanner.l
index 73a1a3f..1d2be76 100644
--- a/src/scanner.l
+++ b/src/scanner.l
@@ -406,6 +406,7 @@ addrstring ({macaddr}|{ip4addr}|{ip6addr})
"rtclassid" { return RTCLASSID; }
"ibriport" { return IBRIPORT; }
"obriport" { return OBRIPORT; }
+"pkttype" { return PKTTYPE; }
"ct" { return CT; }
"direction" { return DIRECTION; }
--
1.7.10.4
parent reply other threads:[~2014-08-05 18:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <53df650e.e335c20a.2c4f.4d82@mx.google.com>]
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=1407263619-4573-1-git-send-email-anarey@gmail.com \
--to=anarey@gmail.com \
--cc=alvaroneay@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).