From: Alexander Mikhalitsyn <alexander.mikhalitsyn@virtuozzo.com>
To: Florian Westphal <fw@strlen.de>
Cc: "netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
"pablo@netfilter.org" <pablo@netfilter.org>
Subject: Re: [iptables PATCH v2 2/2] extensions: libxt_conntrack: print xlate status as set
Date: Wed, 31 Mar 2021 13:31:55 +0300 [thread overview]
Message-ID: <20210331133155.24a1ef3872e4e1873c66338c@virtuozzo.com> (raw)
In-Reply-To: <20210330182136.GC17285@breakpoint.cc>
Hi, Florian,
On Tue, 30 Mar 2021 20:21:36 +0200
Florian Westphal <fw@strlen.de> wrote:
> Alexander Mikhalitsyn <alexander.mikhalitsyn@virtuozzo.com> wrote:
> > Hi Florian,
> >
> > Thank you!
> > So, I need to fix nft and support that syntax?
>
> That would be one way. The other is to fix the != translation
> to use binary logic (the example i gave).
I've prepared 3rd version of patchset.
>
> > Do I understand correctly, that the same issue for state flags like
> > "established, related, ..."?
>
> Yes and no. A connection can't be both established and related at the
> same time, so anonymous set will work in that case.
Got it.
Thank you very much!
Regards,
Alex
prev parent reply other threads:[~2021-03-31 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 14:15 [iptables PATCH v2 1/2] extensions: libxt_conntrack: print xlate state as set Alexander Mikhalitsyn
2021-03-30 14:15 ` [iptables PATCH v2 2/2] extensions: libxt_conntrack: print xlate status " Alexander Mikhalitsyn
2021-03-30 17:39 ` Florian Westphal
2021-03-30 18:05 ` Alexander Mikhalitsyn
2021-03-30 18:21 ` Florian Westphal
2021-03-31 10:31 ` Alexander Mikhalitsyn [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=20210331133155.24a1ef3872e4e1873c66338c@virtuozzo.com \
--to=alexander.mikhalitsyn@virtuozzo.com \
--cc=fw@strlen.de \
--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).