On Tue, 25 Feb 2020, Ondrej Zajicek wrote:
> On Mon, Feb 24, 2020 at 09:25:23PM +0100, Robert Scheck wrote:
> > show route for 209.24.0.3 filtered # Doesn't work
>
> This does not work as expected, because longest-prefix-match code ('for')
> checks just existing routes - i.e. it finds best matching prefix with valid
> routes, and then shows filtered routes on that prefix. That is probably not
> what users expect.
>
> Question is how it should behave - it seems to me that it should do
> best-match just between filtered routes. Any opinion?
My expectation was finding best matching prefix with filtered routes (thus
the same behaviour like for valid routes).
Regards,
Robert
