From: Florian Westphal <fw@strlen.de>
To: Phil Sutter <phil@nwl.cc>,
"Serguei Bezverkhi (sbezverk)" <sbezverk@cisco.com>,
Florian Westphal <fw@strlen.de>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: Proxy load balancer rules
Date: Fri, 31 Jan 2020 23:05:58 +0100 [thread overview]
Message-ID: <20200131220558.GI795@breakpoint.cc> (raw)
In-Reply-To: <20200131140909.GR28318@orbyte.nwl.cc>
Phil Sutter <phil@nwl.cc> wrote:
> Hi Serguei,
>
> On Thu, Jan 30, 2020 at 05:12:07PM +0000, Serguei Bezverkhi (sbezverk) wrote:
> [...]
> >
> > !
> > ! -m recent --rcheck --seconds 10800 --reap --rsource - keywords I am looking for equivalent in nftables
> > !
> >
> > -A KUBE-XLB-BAJ42O6WMSSB7YGA -m comment --comment "services-9837/affinity-lb-esipp-transition:" -m recent --rcheck --seconds 10800 --reap --name KUBE-SEP-JAOQ4ZBNFGZ34AZ4 --mask 255.255.255.255 --rsource -j KUBE-SEP-JAOQ4ZBNFGZ34AZ4
> > -A KUBE-XLB-BAJ42O6WMSSB7YGA -m comment --comment "services-9837/affinity-lb-esipp-transition:" -m recent --rcheck --seconds 10800 --reap --name KUBE-SEP-WLHDVQTL57VBPURE --mask 255.255.255.255 --rsource -j KUBE-SEP-WLHDVQTL57VBPURE
> > -A KUBE-XLB-BAJ42O6WMSSB7YGA -m comment --comment "services-9837/affinity-lb-esipp-transition:" -m recent --rcheck --seconds 10800 --reap --name KUBE-SEP-5XWCIKNI3M4MWAMU --mask 255.255.255.255 --rsource -j KUBE-SEP-5XWCIKNI3M4MWAMU
>
> There is no direct equivalent for recent extension in nftables (yet).
Do we need one? All use cases I've seen can be handled via set infra.
next prev parent reply other threads:[~2020-01-31 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 17:12 Proxy load balancer rules Serguei Bezverkhi (sbezverk)
2020-01-31 14:09 ` Phil Sutter
2020-01-31 22:05 ` Florian Westphal [this message]
2020-02-03 6:56 ` Phil Sutter
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=20200131220558.GI795@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=sbezverk@cisco.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.