From: "Serguei Bezverkhi (sbezverk)" <sbezverk@cisco.com>
To: Florian Westphal <fw@strlen.de>
Cc: Dan Williams <dcbw@redhat.com>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: nft equivalent of iptables command
Date: Thu, 22 Aug 2019 15:24:28 +0000 [thread overview]
Message-ID: <8F2DB50D-3BD2-438F-9A89-E3C166E5CF05@cisco.com> (raw)
In-Reply-To: <20190822151616.GI20113@breakpoint.cc>
On 2019-08-22, 11:16 AM, "Florian Westphal" <fw@strlen.de> wrote:
Serguei Bezverkhi (sbezverk) <sbezverk@cisco.com> wrote:
> That was exactly what I thought about "-s !<ClusterCIDR>" when I saw Florian reply. I will use it for now in nft rules which nft kube-proxy builds for this specific case.
I think that in ideal case, no rules would be generated on the fly,
and that instead it should add/remove elements from nftables maps and sets.
Great idea, once we have API implemented for maps I will give it a try to see how it would fit into proxy logic.
next prev parent reply other threads:[~2019-08-22 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 13:57 nft equivalent of iptables command Serguei Bezverkhi (sbezverk)
2019-08-22 14:16 ` Florian Westphal
2019-08-22 14:49 ` Dan Williams
2019-08-22 15:04 ` Serguei Bezverkhi (sbezverk)
2019-08-22 15:16 ` Florian Westphal
2019-08-22 15:24 ` Serguei Bezverkhi (sbezverk) [this message]
2019-08-22 15:04 ` Serguei Bezverkhi (sbezverk)
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=8F2DB50D-3BD2-438F-9A89-E3C166E5CF05@cisco.com \
--to=sbezverk@cisco.com \
--cc=dcbw@redhat.com \
--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).