show route for ... filtered (not working)

[Ondrej Zajicek]

On Mon, May 13, 2019 at 07:12:53AM -0700, Terra Nova wrote:
> Hi Alexander,
> 
> On Sun, May 12, 2019 at 12:21 AM Alexander Zubkov <green at qrator.net> wrote:
> 
> > Hi,
> >
> > I suppose it could happen because "for" is looking for an active route
> > for the given destination. And filtered routes would not be matched.
> >
> I was leaning in that direction as well, however in the canonical sense,
> using the keyword 'filtered' should have removed that constraint and
> returned the filtered + non-active route.  At this point, I don't know if
> current behavior is the intended behavior.

Hi

This seems to be unintended behavior, but it is hard to say what should
be the intended behavior. I see three possible behaviors:

1) Explicitly forbid this combination (like combination of 'filtered' and
'export' is forbidden).

2) Find and show longest-match between filtered routes.

3) Find longest-match between both valid and filtered routes,
show it only if it is filtered.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."