public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind•com>
To: David Ahern <dsa@cumulusnetworks•com>,
	netdev@vger•kernel.org, stephen@networkplumber•org
Subject: Re: [iproute2 net-next v2 0/3] ip netconf improvements
Date: Fri, 24 Mar 2017 09:37:40 +0100	[thread overview]
Message-ID: <77c62847-e1ae-ebda-64ae-7e04fecbace7@6wind.com> (raw)
In-Reply-To: <1490323882-11609-1-git-send-email-dsa@cumulusnetworks.com>

Le 24/03/2017 à 03:51, David Ahern a écrit :
> Currently, ip netconf only shows data for ipv4 and ipv6 for dumps
> and just ipv4 for device requests. Improve the user experience by
> using the new kernel patch to dump all address families that have
> registered. For example, if mpls_router module is loaded then mpls
> values are displayed along with ipv4 and ipv6.
> 
> If the new feature is not supported (new iproute2 on older kernel)
> the kernel returns the nlmsg error EOPNOTSUPP which can be trapped
> and fallback to existing behavior.
Acked-by: Nicolas Dichtel <nicolas.dichtel@6wind•com>

  parent reply	other threads:[~2017-03-24  8:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24  2:51 [iproute2 net-next v2 0/3] ip netconf improvements David Ahern
2017-03-24  2:51 ` [iproute2 net-next v2 1/3] netlink: Add flag to suppress print of nlmsg error David Ahern
2017-03-24  2:51 ` [iproute2 net-next v2 2/3] ip netconf: Show all address families by default in dumps David Ahern
2017-03-24  2:51 ` [iproute2 net-next v2 3/3] ip netconf: show all families on dev request David Ahern
2017-03-24  8:37 ` Nicolas Dichtel [this message]
2017-04-04 21:07 ` [iproute2 net-next v2 0/3] ip netconf improvements David Ahern
2017-04-04 21:39   ` Stephen Hemminger
2017-04-05 12:18     ` David Ahern
2017-04-14 23:02 ` 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=77c62847-e1ae-ebda-64ae-7e04fecbace7@6wind.com \
    --to=nicolas.dichtel@6wind$(echo .)com \
    --cc=dsa@cumulusnetworks$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=stephen@networkplumber$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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