Strange work of print/find filters

I have three routing tables: inet1, inet2 and main:

[admin@router] /ip route> print detail
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
 0 A S  dst-address=0.0.0.0/0 gateway=127.127.127.1
        gateway-status=127.127.127.1 recursive via 127.127.127.101 inet1 distance=1
        scope=30 target-scope=10 routing-mark=inet1

 1   S  dst-address=0.0.0.0/0 gateway=127.127.127.2
        gateway-status=127.127.127.2 recursive via 127.127.127.102 inet2 distance=2
        scope=30 target-scope=10 routing-mark=inet1

 2 A S  dst-address=0.0.0.0/0 gateway=127.127.127.2
        gateway-status=127.127.127.2 recursive via 127.127.127.102 inet2 distance=1
        scope=30 target-scope=10 routing-mark=inet2

 3   S  dst-address=0.0.0.0/0 gateway=127.127.127.1
        gateway-status=127.127.127.1 recursive via 127.127.127.101 inet1 distance=2
        scope=30 target-scope=10 routing-mark=inet2

 4 ADS  dst-address=10.0.0.0/8 gateway=10.1.132.1
        gateway-status=10.1.132.1 reachable local distance=11 scope=30
        target-scope=10 vrf-interface=local

...

This filter selects the routes from all routing tables:

[admin@router] /ip route> print detail where active
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
 0 A S  dst-address=0.0.0.0/0 gateway=127.127.127.1
        gateway-status=127.127.127.1 recursive via 127.127.127.101 inet1 distance=1
        scope=30 target-scope=10 routing-mark=inet1

 2 A S  dst-address=0.0.0.0/0 gateway=127.127.127.2
        gateway-status=127.127.127.2 recursive via 127.127.127.102 inet2 distance=1
        scope=30 target-scope=10 routing-mark=inet2

 4 ADS  dst-address=10.0.0.0/8 gateway=10.1.132.1
        gateway-status=10.1.132.1 reachable local distance=11 scope=30
        target-scope=10 vrf-interface=local

...

This filter selects only the routes from the routing table inet1:

[admin@router] /ip route> print detail where dst-address=0.0.0.0/0
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
 0 A S  dst-address=0.0.0.0/0 gateway=127.127.127.1
        gateway-status=127.127.127.1 recursive via 127.127.127.101 inet1 distance=1
        scope=30 target-scope=10 routing-mark=inet1

 1   S  dst-address=0.0.0.0/0 gateway=127.127.127.2
        gateway-status=127.127.127.2 recursive via 127.127.127.102 inet2 distance=2
        scope=30 target-scope=10 routing-mark=inet1

Why? Is this a bug?

I can confirm that at least on v3.27 ‘dst-address’ show strange results

what version do you test?

I’m using 5.0rc10.

I’ve sent a bug report to support@.

keep us informed =)