Hi Maria,
thank you for the superfast response, that I kind of seem to have slept through
;-)
So what you mean is creating the /24 route in "static" (possibly in an if
statement) and then matching it later?
I'll try this. The setup is really simple enough.
Thanks,
Elmar.
[email protected] (Maria Matějka) wrote:
> Hello,
> Prefix aggregation is currently not supported. It's quite a lot of work to do
> it properly.
> As a workaround, you may export these routes to an auxiliary kernel table,
> run an external script to maintain the aggregated route and learn the result
> back to BIRD. Or you can simply use the static protocol if your use case is
> simple enough.
> Maria
>
> On June 20, 2020 7:36:47 PM GMT+02:00, "Elmar K. Bins" <[email protected]> wrote:
> >Hi guys,
> >
> >(status update: no solution for the OSPFv3 <--> IOS XR yet, no idea
> >where to look, both sides pretend to be happy but are not)
> >
> >So....
> >
> >I need to create a prefix to be BGP-advertised to peers and transits;
> >this
> >would look like:
> >
> >if (net = xxx/32) {
> > remove it and replace by yyy/zz;
> >}
> >
> >(more or less standard prefix aggregation on the border)
> >
> >
> >I could not find a hint of documentation in regard of doing a thing
> >like this,
> >where should I look?
> >
> >(We are currently forced to configure the wrong netmasks on loopback
> >addresses,
> >so BIRD has something to export)
> >
> >Yours,
> > Elmar.
>
