public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: [iproute2 net-next] ip route: Add RTM_F_LOOKUP_TABLE flag and show table id
Date: Wed, 23 Sep 2015 16:14:37 -0700	[thread overview]
Message-ID: <20150923161437.7e055fc2@urahara> (raw)
In-Reply-To: <1442859588-14831-1-git-send-email-dsa@cumulusnetworks.com>

On Mon, 21 Sep 2015 11:19:48 -0700
David Ahern <dsa@cumulusnetworks.com> wrote:

> Currently 'ip route get' does not show the table the lookup result comes
> from and prior to kernel commit c36ba6603a11 the response from the kernel
> was hardcoded to the main table. From the discussion this appears to be
> a leftover from the route cache where the cached entry lost the table id
> and so the result was hardcoded to main table.
> 
> c36ba6603a11 added the RTM_F_LOOKUP_TABLE flag to maintain that behavior
> but to allow new tools to ask for the actual table id for the lookup.
> This patch adds that flag to ip route get request and if the result is
> not the main table shows the table id.
> 
> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>

Applied, the compatibility concerns seem to be abated.

      parent reply	other threads:[~2015-09-23 23:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 18:19 [iproute2 net-next] ip route: Add RTM_F_LOOKUP_TABLE flag and show table id David Ahern
2015-09-21 21:19 ` Stephen Hemminger
2015-09-21 21:28   ` David Ahern
2015-09-21 21:58     ` David Miller
2015-09-21 22:03       ` David Ahern
2015-09-21 22:03         ` David Miller
2015-09-21 22:23           ` David Ahern
2015-09-21 22:36             ` David Miller
2015-09-23 23:14 ` 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=20150923161437.7e055fc2@urahara \
    --to=stephen@networkplumber.org \
    --cc=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