From: David Ahern <dsahern@gmail.com>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 net-next v5] iprule: support for ip_proto, sport and dport match options
Date: Thu, 8 Mar 2018 11:14:23 -0700 [thread overview]
Message-ID: <439a2ed6-a242-e0a9-1a8a-a8a86d2665e0@gmail.com> (raw)
In-Reply-To: <1520532407-22966-1-git-send-email-roopa@cumulusnetworks.com>
On 3/8/18 11:06 AM, Roopa Prabhu wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> add support to match on ip_proto, sport and dport ranges.
> For ip_proto, this patch currently enumerates, tcp, udp and sctp.
> This list can be extended in the future.
>
> example:
> $ip rule add sport 666-777 dport 999 ip_proto tcp table 100
> $ip rule show
> 0: from all lookup local
> 32765: from all ip_proto 6 sport 666-777 dport 999 lookup 100
> 32766: from all lookup main
> 32767: from all lookup default
>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
> ---
> v2: use inet_proto_* as suggested by David Ahern
>
> v3: fix newlines in usage (feedback from David Ahern)
>
> v4: fixes for json (feedback from Stephen H).
>
> v5: drop uapi header update from patch, use int for inet_proto_a2n
> return val to catch invalid proto errors, rename ip_proto to ipproto
> to be consistent with tc
>
> ip/iprule.c | 67 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> man/man8/ip-rule.8 | 32 +++++++++++++++++++++++++-
> 2 files changed, 98 insertions(+), 1 deletion(-)
>
applied to iproute2-next
prev parent reply other threads:[~2018-03-08 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 18:06 [PATCH iproute2 net-next v5] iprule: support for ip_proto, sport and dport match options Roopa Prabhu
2018-03-08 18:14 ` 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=439a2ed6-a242-e0a9-1a8a-a8a86d2665e0@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.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).