From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 net-next] iproute: extend route get for mpls routes
Date: Tue, 18 Jul 2017 17:15:02 -0700 [thread overview]
Message-ID: <20170718171502.2e60581e@xeon-e3> (raw)
In-Reply-To: <1499465291-2199-1-git-send-email-roopa@cumulusnetworks.com>
On Fri, 7 Jul 2017 15:08:11 -0700
Roopa Prabhu <roopa@cumulusnetworks.com> wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This patch extends route get to support mpls specific
> route attributes like RTA_NEWDST.
>
> Input:
> RTA_DST - input label
> RTA_NEWDST - labels in packet for multipath selection
>
> By default the getroute handler returns matched
> nexthop label, via and oif
>
> With fibmatch keyword (RTM_F_FIB_MATCH flag), full matched
> route is returned.
>
> example:
> $ip -f mpls route show
> 101
> nexthop as to 102/103 via inet 172.16.2.2 dev virt1-2
> nexthop as to 302/303 via inet 172.16.12.2 dev virt1-12
> 201
> nexthop as to 202/203 via inet6 2001:db8:2::2 dev virt1-2
> nexthop as to 402/403 via inet6 2001:db8:12::2 dev virt1-12
>
> $ip -f mpls route get 103
> RTNETLINK answers: Network is unreachable
>
> $ip -f mpls route get 101
> 101 as to 102/103 via inet 172.16.2.2 dev virt1-2
>
> $ip -f mpls route get as to 302/303 101
> 101 as to 302/303 via inet 172.16.12.2 dev virt1-12
>
> $ip -f mpls route get fibmatch 103
> RTNETLINK answers: Network is unreachable
>
> $ip -f mpls route get fibmatch 101
> 101
> nexthop as to 102/103 via inet 172.16.2.2 dev virt1-2
> nexthop as to 302/303 via inet 172.16.12.2 dev virt1-12
>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Applied, thanks.
prev parent reply other threads:[~2017-07-19 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 22:08 [PATCH iproute2 net-next] iproute: extend route get for mpls routes Roopa Prabhu
2017-07-19 0:15 ` Stephen Hemminger [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=20170718171502.2e60581e@xeon-e3 \
--to=stephen@networkplumber.org \
--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