From: David Ahern <dsahern@gmail.com>
To: Michal Kubecek <mkubecek@suse.cz>, netdev@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
emersonbernier@tutanota.com,
Stephen Hemminger <stephen@networkplumber.org>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
David Miller <davem@davemloft.net>,
piraty1@inbox.ru
Subject: Re: 5.1 `ip route get addr/cidr` regression
Date: Fri, 17 May 2019 09:20:56 -0600 [thread overview]
Message-ID: <cb462836-a8d3-b8d8-fe3f-42186ade769e@gmail.com> (raw)
In-Reply-To: <20190517141709.GA25473@unicorn.suse.cz>
On 5/17/19 8:17 AM, Michal Kubecek wrote:
> AFAIK the purpose of 'ip route get' always was to let the user check
> the result of a route lookup, i.e. "what route would be used if I sent
> a packet to an address". To be honest I would have to check how exactly
> was "ip route get <addr>/<prefixlen>" implemented before.
>
The prefixlen was always silently ignored. We are trying to clean up
this 'silent ignoring' just hitting a few speed bumps.
next prev parent reply other threads:[~2019-05-17 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 13:00 [BUG][iproute2][5.0] ip route show table default: "Error: ipv4: FIB table does not exist." emersonbernier
2019-03-24 14:17 ` David Ahern
2019-03-24 17:02 ` emersonbernier
2019-03-24 17:20 ` David Ahern
2019-03-24 17:34 ` emersonbernier
2019-03-24 17:36 ` David Ahern
2019-03-24 18:29 ` Michal Kubecek
2019-03-24 18:36 ` Michal Kubecek
2019-03-24 22:09 ` David Ahern
2019-05-02 13:17 ` emersonbernier
2019-05-09 2:24 ` David Ahern
2019-05-17 10:22 ` 5.1 `ip route get addr/cidr` regression Jason A. Donenfeld
2019-05-17 14:17 ` Michal Kubecek
2019-05-17 15:20 ` David Ahern [this message]
2019-05-17 15:22 ` Jason A. Donenfeld
2019-05-17 15:17 ` David Ahern
2019-05-17 17:35 ` Stephen Hemminger
2019-05-17 17:39 ` David Ahern
2019-05-17 20:19 ` Jason A. Donenfeld
2019-05-17 20:30 ` Jason A. Donenfeld
2019-05-17 17:40 ` David Ahern
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=cb462836-a8d3-b8d8-fe3f-42186ade769e@gmail.com \
--to=dsahern@gmail.com \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=emersonbernier@tutanota.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=piraty1@inbox.ru \
--cc=stephen@networkplumber.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).