From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Elise Lennion <elise.lennion@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft v2] src: Allow to list ruleset without stateful information
Date: Mon, 16 Jan 2017 22:07:14 +0100 [thread overview]
Message-ID: <20170116210714.GA20884@salvia> (raw)
In-Reply-To: <20170116210533.GA20792@salvia>
On Mon, Jan 16, 2017 at 10:05:33PM +0100, Pablo Neira Ayuso wrote:
> On Mon, Jan 16, 2017 at 06:40:40PM -0200, Elise Lennion wrote:
> > Currently only counter and quota have stateful information.
> >
> > For named counters, packets and bytes are displayed as 0.
> >
> > Standard list ruleset:
> >
> > table ip filter {
> > counter https {
> > packets 161942 bytes 10253353
> > }
> >
> > chain output {
> > type filter hook output priority 0; policy accept;
> > counter name tcp dport map { https : "https"}
> > tcp dport https counter packets 171211 bytes 10869045
> > tcp dport https quota 25 mbytes used 10 mbytes
> > }
> > }
> >
> > With stateless option, -s:
> >
> > table ip filter {
> > counter https {
> > packets 0 bytes 0
> > }
> >
> > chain output {
> > type filter hook output priority 0; policy accept;
> > counter name tcp dport map { https : "https"}
> > tcp dport https counter
> > tcp dport https quota 25 mbytes
> > }
> > }
>
> Applied, thanks Elise.
BTW, could you send me a patch to update nft-tests.py to use '-s'
option? So we don't get spurious errors when checking for rules with
stateful expressions and objects while there's traffic going on on the
testbed machine. I would forecast a oneliner patch for this.
Thanks.
prev parent reply other threads:[~2017-01-16 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 20:40 [PATCH nft v2] src: Allow to list ruleset without stateful information Elise Lennion
2017-01-16 21:05 ` Pablo Neira Ayuso
2017-01-16 21:07 ` 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=20170116210714.GA20884@salvia \
--to=pablo@netfilter.org \
--cc=elise.lennion@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).