From: Simon Horman <simon.horman@netronome.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
Dinan Gunawardena <dinan.gunawardena@netronome.com>,
netdev@vger.kernel.org, oss-drivers@netronome.com,
Simon Horman <simon.horman@netronome.com>
Subject: [PATCH iproute2/net-next repost 0/3] tc: flower: support masked ICMP code and type match
Date: Thu, 9 Feb 2017 14:48:58 +0100 [thread overview]
Message-ID: <1486648141-22955-1-git-send-email-simon.horman@netronome.com> (raw)
Hi,
this short series allows the tc tool to configure masked matches on the
ICMP code and type. Unmasked matches are already supported by the tool.
This does not depend on any kernel changes as support for both masked and
unmasked matches were added to the kernel at the same time.
Sample usage:
tc qdisc add dev eth0 ingress
tc filter add dev eth0 protocol ipv6 parent ffff: flower \
indev eth0 ip_proto icmpv6 type 128/240 code 0 action drop
Reposting after breaking out of a larger patchset.
Simon Horman (3):
tc: flower: provide generic masked u8 parser helper
tc: flower: provide generic masked u8 print helper
tc: flower: support masked ICMP code and type match
man/man8/tc-flower.8 | 16 ++++--
tc/f_flower.c | 158 ++++++++++++++++++++++++++++++++++-----------------
2 files changed, 119 insertions(+), 55 deletions(-)
--
2.7.0.rc3.207.g0ac5344
next reply other threads:[~2017-02-09 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:48 Simon Horman [this message]
2017-02-09 13:48 ` [PATCH iproute2/net-next repost 1/3] tc: flower: provide generic masked u8 parser helper Simon Horman
2017-02-09 13:49 ` [PATCH iproute2/net-next repost 2/3] tc: flower: provide generic masked u8 print helper Simon Horman
2017-02-09 13:49 ` [PATCH iproute2/net-next repost 3/3] tc: flower: support masked ICMP code and type match Simon Horman
2017-02-19 0:14 ` [PATCH iproute2/net-next repost 0/3] " Stephen Hemminger
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=1486648141-22955-1-git-send-email-simon.horman@netronome.com \
--to=simon.horman@netronome.com \
--cc=dinan.gunawardena@netronome.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=stephen@networkplumber.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).