From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alvaro Neira Ayuso <alvaroneay@gmail.com>
Cc: netfilter-devel@vger.kernel.org, eric@regit.org, kaber@trash.net
Subject: Re: [nftables PATCH v2] queue: More compact syntax
Date: Wed, 11 Jun 2014 11:13:52 +0200 [thread overview]
Message-ID: <20140611091352.GA5201@localhost> (raw)
In-Reply-To: <1402406784-15693-1-git-send-email-alvaroneay@gmail.com>
On Tue, Jun 10, 2014 at 03:26:24PM +0200, Alvaro Neira Ayuso wrote:
> This patch allows to use a new syntax more compact and break
> the current syntax. This new syntax is more similar than the nftables
> syntax that we use usually. We can use range like we have used in
> other case in nftables. Here, we have some examples:
>
> Before, If we want to declare a queue, we have used a syntax like this:
>
> nft add rule test input queue num 1 total 3 options bypass,fanout
>
> If we want to use the queue number 1 and the two next (total 3),
> we use a range in the new syntax, for example:
>
> nft add rule test input queue num 1-3 bypass fanout
>
> Also if we want to use only one queue, the new rules are like:
>
> nft add rule test input queue num 1 //queue 1
> or
> nft add rule test input queue //queue 0
>
> And if we want to add a specific flags we only need to put
> what flags we want to use:
>
> nft add rule test input queue bypass
>
> we don't need to use options and the comma for indicating the
> flags.
Applied, thanks Álvaro.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-06-11 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1402406110-14892-1-git-send-email-alvaroneay@gmail.com>
2014-06-10 13:26 ` [nftables PATCH v2] queue: More compact syntax Alvaro Neira Ayuso
2014-06-11 9:13 ` Pablo Neira Ayuso [this message]
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=20140611091352.GA5201@localhost \
--to=pablo@netfilter.org \
--cc=alvaroneay@gmail.com \
--cc=eric@regit.org \
--cc=kaber@trash.net \
--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).