Missing route that is shown in filter used by eBGP

Ondrej Zajicek santiago at crfreenet.org
Fri Nov 21 15:22:55 CET 2025


On Fri, Nov 21, 2025 at 01:37:57PM +0100, Maximilian Wilhelm via Bird-users wrote:
> Hi folks,
> 
> Anno domini 2025 Maria Matejka via Bird-users scripsit:
> 
> > > - b) filter output vs. export reality
> > >   Independent of whether we filter on "all best" or "all routes", in the
> > >   CLI the filter output shown does include the route - if the filter
> > >   does not match, it also should not print it
> > 
> > Well, if you do `show route filter xyz`, then you get all routes
> > matching that filter. Some protocols pick them. You can do `show route
> > export bgp_to_internet.ipv6` to explicitly re-run the export filter in
> > that context.
> > 
> > I know that it is kinda confusing, and we should probably improve our
> > documentation to show this properly.
> 
> A `show route primary filter xyz` should also be equivalent to what's
> actually exported, right?

No, because a protocol could reject (or even accept) a route on its own,
regardless of its export filter. For example an IBGP protocol rejects routes
recived from other IBGP protocols.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
"To err is human -- to blame it on a computer is even more so."


More information about the Bird-users mailing list