From: David Ahern <dsahern@gmail.com>
To: Paul Blakey <paulb@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
Roi Dayan <roid@nvidia.com>, Yossi Kuperman <yossiku@nvidia.com>,
Oz Shlomo <ozsh@nvidia.com>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Aaron Conole <aconole@redhat.com>, Zhike Wang <wangzhike@jd.com>
Cc: Rony Efraim <ronye@nvidia.com>,
nst-kernel@redhat.com, John Hurley <john.hurley@netronome.com>,
Simon Horman <simon.horman@netronome.com>,
Justin Pettit <jpettit@ovn.org>
Subject: Re: [PATCH iproute2/net-next] tc: flower: Add support for ct_state reply flag
Date: Thu, 4 Feb 2021 21:58:20 -0700 [thread overview]
Message-ID: <4ae1d0db-f8ec-5369-79a8-76f17f06d70e@gmail.com> (raw)
In-Reply-To: <1612268682-29525-1-git-send-email-paulb@nvidia.com>
On 2/2/21 5:24 AM, Paul Blakey wrote:
> Matches on conntrack rpl ct_state.
>
> Example:
> $ tc filter add dev ens1f0_0 ingress prio 1 chain 1 proto ip flower \
> ct_state +trk+est+rpl \
> action mirred egress redirect dev ens1f0_1
> $ tc filter add dev ens1f0_1 ingress prio 1 chain 1 proto ip flower \
> ct_state +trk+est-rpl \
> action mirred egress redirect dev ens1f0_0
>
> Signed-off-by: Paul Blakey <paulb@nvidia.com>
> ---
> man/man8/tc-flower.8 | 2 ++
> tc/f_flower.c | 1 +
> 2 files changed, 3 insertions(+)
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2021-02-05 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 12:24 [PATCH iproute2/net-next] tc: flower: Add support for ct_state reply flag Paul Blakey
2021-02-02 12:41 ` Marcelo Ricardo Leitner
2021-02-03 7:56 ` Paul Blakey
2021-02-05 4:58 ` David Ahern [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=4ae1d0db-f8ec-5369-79a8-76f17f06d70e@gmail.com \
--to=dsahern@gmail.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=john.hurley@netronome.com \
--cc=jpettit@ovn.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nst-kernel@redhat.com \
--cc=ozsh@nvidia.com \
--cc=paulb@nvidia.com \
--cc=roid@nvidia.com \
--cc=ronye@nvidia.com \
--cc=simon.horman@netronome.com \
--cc=wangzhike@jd.com \
--cc=yossiku@nvidia.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 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).