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. On Sun, May 12, 2019 at 3:57 AM Terra Nova <terratech@gmail.com> wrote:
Greetings,
Ubuntu-16.04.6 LTS bird-1.6.6 (built from source)
Our upstream BGP configuration is using: import keep filtered on
I was checking the master table for a (filtered) destination IPv6 address (and network) doing the following. bird> show route for 2620:0:6b0:ff00::20 Network not in table
bird> show route for 2620:0:6b0:ff00::20 all Network not in table
bird> show route for 2620:0:6b0:ff00::20 filtered Network not in table
bird> show route where bgp_path ~ [= * 23028 =]
bird> show route where bgp_path ~ [= * 23028 =] filtered 2604:8800::/32 via 2001:590::xxxx:xxxx on edge.411 [gtt6 01:53:36] * (100 / 95) [AS 820048060 174 23028i] 2620:0:6b0::/48 via 2001:590::xxxx:xxxx on edge.411 [gtt6 01:53:36] * (100 / 95) [AS 820048060 174 23028i]
bird> show route filtered for 2604:8800::/32 Network not in table
bird> show route for 2604:8800::/32 filtered Network not in table
bird> show route for 2620:0:6b0::/48 filtered Network not in table
bird> show route table master for 2620:0:6b0:ff00::20 filtered Network not in table
Why will the 'show route' only show this filtered route using 'bgp_path' and not directly using 'for'? This route is filtered in the 'master' table and there are no Pipes being used. Am I misusing the 'filtered' option?
Thank you for looking.
-- Terra