From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, dsahern@gmail.com
Subject: Re: [PATCH net-next] net: Lookup actual route when oif is VRF device
Date: Wed, 07 Oct 2015 04:31:40 -0700 (PDT) [thread overview]
Message-ID: <20151007.043140.2292153680902956363.davem@davemloft.net> (raw)
In-Reply-To: <1444067344-31144-1-git-send-email-dsa@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Mon, 5 Oct 2015 10:49:04 -0700
> If the user specifies a VRF device in a get route query the custom route
> pointing to the VRF device is returned:
>
> $ ip route ls table vrf-red
> unreachable default
> broadcast 10.2.1.0 dev eth1 proto kernel scope link src 10.2.1.2
> 10.2.1.0/24 dev eth1 proto kernel scope link src 10.2.1.2
> local 10.2.1.2 dev eth1 proto kernel scope host src 10.2.1.2
> broadcast 10.2.1.255 dev eth1 proto kernel scope link src 10.2.1.2
>
> $ ip route get oif vrf-red 10.2.1.40
> 10.2.1.40 dev vrf-red
> cache
>
> Add the flags to skip the custom route and go directly to the FIB. With
> this patch the actual route is returned:
>
> $ ip route get oif vrf-red 10.2.1.40
> 10.2.1.40 dev eth1 src 10.2.1.2
> cache
>
> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
Applied, thank
prev parent reply other threads:[~2015-10-07 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 17:49 [PATCH net-next] net: Lookup actual route when oif is VRF device David Ahern
2015-10-05 18:01 ` kbuild test robot
2015-10-05 18:10 ` David Ahern
2015-10-11 14:27 ` [kbuild-all] " Fengguang Wu
2015-10-07 11:31 ` David Miller [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=20151007.043140.2292153680902956363.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=dsahern@gmail.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).