netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Liping Zhang" <zlpnobody@163.com>
To: "Florian Westphal" <fw@strlen.de>
Cc: pablo@netfilter.org, netfilter-devel@vger.kernel.org,
	"Liping Zhang" <liping.zhang@spreadtrum.com>
Subject: Re: [PATCH iptables] extensions: libxt_connlabel: Add translation to nft
Date: Sat, 16 Jul 2016 17:28:34 +0800 (CST)	[thread overview]
Message-ID: <8a553bc.7699.155f309334d.Coremail.zlpnobody@163.com> (raw)
In-Reply-To: <20160716090439.GA6123@breakpoint.cc>

At 2016-07-16 17:04:39, "Florian Westphal" <fw@strlen.de> wrote:
>Liping Zhang <zlpnobody@163.com> wrote:
>> 
>>   # iptables-translate -A INPUT -m connlabel ! --label bit40 --set
>>   nft add rule ip filter INPUT ct label set bit40 ct label != bit40 counter
>
>Should probably be:
>
>... ct label and bit40 != bit40 ...
>
>!= bit40 will be true if bit40 and another bit is set.

Right, "ct label bit40" and "ct label != bit40" have the different semantics:

# nft add rule filter input ct label bit40 --debug=netlink
ip filter input 
  [ ct load label => reg 1 ]
  [ bitwise reg 1 = (reg=1 & 0x00000000 0x00000100 0x00000000 0x00000000 ) ^ 0x00000000 0x00000000 0x00000000 0x00000000 ]
  [ cmp neq reg 1 0x00000000 0x00000000 0x00000000 0x00000000 ]

# nft add rule filter input ct label != bit40 --debug=netlink
ip filter input 
  [ ct load label => reg 1 ]
  [ cmp neq reg 1 0x00000000 0x00000100 0x00000000 0x00000000 ]

Will send V2 later, Thanks.

      reply	other threads:[~2016-07-16  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-16  6:15 [PATCH iptables] extensions: libxt_connlabel: Add translation to nft Liping Zhang
2016-07-16  9:04 ` Florian Westphal
2016-07-16  9:28   ` Liping Zhang [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=8a553bc.7699.155f309334d.Coremail.zlpnobody@163.com \
    --to=zlpnobody@163.com \
    --cc=fw@strlen.de \
    --cc=liping.zhang@spreadtrum.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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).