From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alvaro Neira Ayuso <alvaroneay@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nftables PATCH] src: Add support for adding TOS symbols
Date: Fri, 23 May 2014 20:26:53 +0200 [thread overview]
Message-ID: <20140523182653.GA3658@localhost> (raw)
In-Reply-To: <1400868602-23142-1-git-send-email-alvaroneay@gmail.com>
On Fri, May 23, 2014 at 08:10:02PM +0200, Alvaro Neira Ayuso wrote:
> This patch allows to add type of service using symbols not
> only with mask.
>
> Signed-off-by: Alvaro Neira Ayuso <alvaroneay@gmail.com>
> ---
> include/datatype.h | 2 ++
> src/proto.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++-
> 2 files changed, 61 insertions(+), 1 deletion(-)
>
> diff --git a/include/datatype.h b/include/datatype.h
> index 2c66e9d..b53358c 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_TOS: Type of service
^^^^^
Minor nitpick: Missing comment above regarding the subtype.
> */
> enum datatypes {
> TYPE_INVALID,
> @@ -63,6 +64,7 @@ enum datatypes {
> TYPE_TC_HANDLE,
> TYPE_UID,
> TYPE_GID,
> + TYPE_TOS,
You have to add this to the end of the list of enum.
The datatypes are used in the sets keytype, nft needs them to
interpret the elements. If you add this here and someone upgrades nft,
it will break.
> TYPE_CT_STATE,
> TYPE_CT_DIR,
> TYPE_CT_STATUS,
next prev parent reply other threads:[~2014-05-23 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 18:10 [nftables PATCH] src: Add support for adding TOS symbols Alvaro Neira Ayuso
2014-05-23 18:26 ` Pablo Neira Ayuso [this message]
2014-05-23 19:15 ` [nftables PATCH v2] " Alvaro Neira Ayuso
2014-05-24 5:03 ` Maciej Żenczykowski
2014-05-27 9:59 ` [nftables PATCH 1/2 v3] " Alvaro Neira Ayuso
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=20140523182653.GA3658@localhost \
--to=pablo@netfilter.org \
--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).