On Fri, May 17, 2019 at 5:21 PM David Ahern <dsah...@gmail.com> wrote: > > 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.
Indeed what we were after has always been, `ip route show dev <dev> match <addr>/<prefixlen>`, and the old positive return value from `ip route get` wasn't always correct for what we were using it for. So mostly the breakage exposed another bug here.
