netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC PATCH nft userspace] nft: connlabel matching support
Date: Sun, 16 Feb 2014 17:23:39 +0000	[thread overview]
Message-ID: <20140216172339.GA18357@macbook.localnet> (raw)
In-Reply-To: <20140216165957.GA2408@breakpoint.cc>

On Sun, Feb 16, 2014 at 05:59:57PM +0100, Florian Westphal wrote:
> Patrick McHardy <kaber@trash.net> wrote:
> > Ok I misunderstood your initial problem statement. So basically what it
> > should currently do:
> > 
> > ct labels foo => test whether that bit is set
> > ct labels == foo => test whether foo and only foo is set
> > 
> > Ok I can see the problem :)
> > 
> > The implicit op only selects FLAGCMP for EXPR_LIST (see
> > expr_evaluate_relational()). That should probably be changed to take the
> > base type into account. This also seems wrong for the ct state expression,
> > we currently use equality if only one state is specified but use a flag
> > comparison if multiple flags are specified.
> 
> I hacked something up to also select FLAGCMP for bitmask type.
> 
> $ nft --debug=netlink add rule filter output ct labels foo
> ip filter output 0 0
>  [ ct load labels => reg 1 ]
>  [ bitwise reg 1 = (reg=1 & 0x00000001 0x00000000 0x00000000 0x00000000 ) ^ 0x00000000 0x00000000 0x00000000 0x00000000 ]
>  [ cmp neq reg 1 0x00000001 0x00000000 0x00000000 0x00000000 ]
> 
> looks better.  Still not exactly the same though.
> The cmp neq will cause it to match when the label is not set.
> 
> I then tried again with vanilla master branch:
> tcp flags syn counter packets 0 bytes 0
> tcp flags fin,syn counter packets 184 bytes 24880
> 
> So, same problem there: EXPR_LIST == cmp neq.  Is that intentional?
> It seems wrong to me, e.g.  "tcp flags fin,syn" will match virtually all
> tcp packets.
> 
> Maybe netlink_gen_flagcmp() should generate NFT_CMP_GT i.e.:
>  [ bitwise reg 1 = (reg=1 & 0x00000012 ) ^ 0x00000000 ]
>  [ cmp gt reg 1 0x00000000 ]
> 
> At least that would be what I would have expected :-}
> 
> Am I wrong?

It should actually generate a NEQ 0. Seems this was broken in commit
aae836a7 (src: use libnftables).

Try the attached patch please.

> As a side note, experimenting a bit with tcp flags:
> 
> add rule filter output tcp flags & (syn|ack) == (syn|ack)
> 
> works fine with current master branch.  But list shows
> 
> "tcp flags & 18 == 18", i.e. no symbol translation.
> 
> Shouldn't it restore the symbolic names?
> I think this is the very same problem that I had with my connlabel
> dabbling, so it would be nice if it could be solved in generic way.

Most likely. Please see if the attached patch solves this.

diff --git a/src/netlink_linearize.c b/src/netlink_linearize.c
index 332383a..3e9a078 100644
--- a/src/netlink_linearize.c
+++ b/src/netlink_linearize.c
@@ -285,7 +285,6 @@ static void netlink_gen_flagcmp(struct netlink_linearize_ctx *ctx,
 	netlink_gen_raw_data(zero, expr->right->byteorder, len, &nld);
 	nft_rule_expr_set_u32(nle, NFT_EXPR_CMP_SREG, sreg);
 	nft_rule_expr_set_u32(nle, NFT_EXPR_CMP_OP, NFT_CMP_NEQ);
-	netlink_gen_data(expr->right, &nld);
 	nft_rule_expr_set(nle, NFT_EXPR_CMP_DATA, nld.value, nld.len);
 	nft_rule_add_expr(ctx->nlr, nle);
 

  reply	other threads:[~2014-02-16 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15 22:47 [RFC PATCH nft userspace] nft: connlabel matching support Florian Westphal
2014-02-16  8:53 ` Patrick McHardy
2014-02-16 11:01   ` Florian Westphal
2014-02-16 11:12     ` Patrick McHardy
2014-02-16 11:27       ` Florian Westphal
2014-02-16 11:33         ` Patrick McHardy
2014-02-16 16:59       ` Florian Westphal
2014-02-16 17:23         ` Patrick McHardy [this message]
2014-02-16 17:51           ` Florian Westphal
2014-02-16 17:53             ` Patrick McHardy
2014-02-16 20:41               ` Patrick McHardy

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=20140216172339.GA18357@macbook.localnet \
    --to=kaber@trash.net \
    --cc=fw@strlen.de \
    --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).