From: David Ahern <dsa@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsa@cumulusnetworks.com>
Subject: [PATCH iproute2 0/6] Add support for vrf keyword
Date: Tue, 14 Jun 2016 13:59:26 -0700 [thread overview]
Message-ID: <1465937972-25011-1-git-send-email-dsa@cumulusnetworks.com> (raw)
Currently the syntax for VRF related commands is rather kludgy and
inconsistent from one subcommand to another. This set adds support
for the VRF keyword to the link, address, neigh, and route commands
to improve the user experience listing data associated with vrfs,
modifying routes or doing a route lookup.
David Ahern (6):
ip vrf: Add name_is_vrf
ip link/addr: Add support for vrf keyword
ip neigh: Add support for keyword
ip route: Change type mask to bitmask
ip vrf: Add ipvrf_get_table
ip route: Add support for vrf keyword
ip/ip_common.h | 3 ++
ip/ipaddress.c | 11 ++++++
ip/iplink.c | 15 ++++++-
ip/iplink_vrf.c | 119 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ip/ipneigh.c | 14 ++++++-
ip/iproute.c | 43 ++++++++++++++++----
6 files changed, 195 insertions(+), 10 deletions(-)
--
2.1.4
next reply other threads:[~2016-06-14 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 20:59 David Ahern [this message]
2016-06-14 20:59 ` [PATCH iproute2 1/6] ip vrf: Add name_is_vrf David Ahern
2016-06-14 20:59 ` [PATCH iproute2 2/6] ip link/addr: Add support for vrf keyword David Ahern
2016-06-14 20:59 ` [PATCH iproute2 3/6] ip neigh: Add support for keyword David Ahern
2016-06-14 20:59 ` [PATCH iproute2 4/6] ip route: Change type mask to bitmask David Ahern
2016-06-14 20:59 ` [PATCH iproute2 5/6] ip vrf: Add ipvrf_get_table David Ahern
2016-06-14 20:59 ` [PATCH iproute2 6/6] ip route: Add support for vrf keyword David Ahern
2016-06-24 1:46 ` [PATCH iproute2 0/6] " David Ahern
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=1465937972-25011-1-git-send-email-dsa@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=netdev@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).