[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170605123426.3660e8bf@xeon-e3>
Date: Mon, 5 Jun 2017 12:34:26 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Roopa Prabhu <roopa@...ulusnetworks.com>
Cc: netdev@...r.kernel.org, dsahern@...il.com,
nikolay@...ulusnetworks.com
Subject: Re: [PATCH iproute2] iproute: extend route get to return matching
fib route
On Thu, 1 Jun 2017 21:53:28 -0700
Roopa Prabhu <roopa@...ulusnetworks.com> wrote:
> From: Roopa Prabhu <roopa@...ulusnetworks.com>
>
> Uses newly introduced RTM_GETROUTE flag RTM_F_FIB_MATCH
> to return a matching fib route. Introduces 'fibmatch'
> keyword to ip route get.
>
> ipv4:
> ----
> $ip route show
> default via 192.168.0.2 dev eth0
> 10.0.14.0/24
> nexthop via 172.16.0.3 dev dummy0 weight 1
> nexthop via 172.16.1.3 dev dummy1 weight 1
>
> $ip route get 10.0.14.2
> 10.0.14.2 via 172.16.1.3 dev dummy1 src 172.16.1.1
> cache
>
> $ip route get fibmatch 10.0.14.2
> 10.0.14.0/24
> nexthop via 172.16.0.3 dev dummy0 weight 1
> nexthop via 172.16.1.3 dev dummy1 weight 1
>
> ipv6:
> ----
> $ip -6 route show
> 2001:db9:100::/120 metric 1024
> nexthop via 2001:db8:2::2 dev dummy0 weight 1
> nexthop via 2001:db8:12::2 dev dummy1 weight 1
>
> $ip -6 route get 2001:db9:100::1
> 2001:db9:100::1 from :: via 2001:db8:12::2 dev dummy1 \
> src 2001:db8:12::1 metric 1024 pref medium
>
> $ip -6 route get fibmatch 2001:db9:100::1
> 2001:db9:100::/120 metric 1024
> nexthop via 2001:db8:12::2 dev dummy1 weight 1
> nexthop via 2001:db8:2::2 dev dummy0 weight 1
>
> Signed-off-by: Roopa Prabhu <roopa@...ulusnetworks.com>
Applied to net-next branch
Powered by blists - more mailing lists