On Mon, Jan 15, 2024, 10:15 Lukas Haase wrote:
> Hi Alexander,
>
> Thank you so much!
> Debian has bird2 package as well so I migrated and indeed it works!!
> There must be a bug in bird1 that causes recursive routes in static
> protocol not to resolve...
> As just a minor change to your
Hi,
I cannot tell for bird1, unfortunately. It might not work there at
all. Here is working example for bird2, I tested it and it seems
valid. I export smaller routes to a separate table, so that static
protocol use only those routes for recursive resolution, otherwise it
will also try to use
Hi Alexander
> Gesendet: Sonntag, 14. Januar 2024 um 23:03 Uhr
> Von: "Alexander Zubkov"
> An: "Lukas Haase"
> Cc: bird-users@network.cz
> Betreff: Re: Re: Exporting a larger prefix if a smaller prefix is being
> exported
>
> Hi Lukas,
>
> Two questions.
> You add dummy interface on another
Hi Lukas,
Two questions.
You add dummy interface on another node that propagates it via ospf to
your border?
And the most important one - you use bird version 1?
Regards,
Alexander
On Mon, Jan 15, 2024 at 6:23 AM Lukas Haase wrote:
>
> Hi Alexander,
>
> Thank you again, this is really
Hi Alexander,
Thank you again, this is really promising and I think I get the gist of it.
I have just one issue left: The /24 prefix keeps showing as unreachable.
I have set up a test peer (both sides) to verify that routes come through.
Here is my config:
protocol bgp test
{
local as
Hi Lukas,
On Sun, Jan 14, 2024 at 6:23 AM Lukas Haase wrote:
>
> Hi Alex,
>
> > Gesendet: Samstag, 13. Januar 2024 um 06:31 Uhr
> > Von: "Alexander Zubkov"
> > An: "Lukas Haase"
> > Cc: bird-users@network.cz
> > Betreff: Re: Exporting a larger prefix if a smaller prefix is being exported
> >
>
Hi Alex,
> Gesendet: Samstag, 13. Januar 2024 um 06:31 Uhr
> Von: "Alexander Zubkov"
> An: "Lukas Haase"
> Cc: bird-users@network.cz
> Betreff: Re: Exporting a larger prefix if a smaller prefix is being exported
>
> Hi,
>
> You cannot do "direct" prefix aggregation to a lager prefix in Bird
>
Sorry, sent this off-list by mistake.
Maria
On 13 January 2024 18:11:07 CET, Maria Matejka wrote:
>Hello!
>
>This will be possible in version 3, maybe not fully automatic in the first
>stable versions. There is some code (indirectly) enabling this, waiting for
>some finishing touches amd
Hey Luke,
Lukas Haase via Bird-users writes:
> Hi,
>
> Is is somehow possible to export a larger prefix if one or more sub-prefixes
> (subnets) are exported ... but also remove that prefix if no smaller subnet
> exist any more?
a short story about /24's in the Internet and how to handle
Hi,
You cannot do "direct" prefix aggregation to a lager prefix in Bird
yet. But there are some ways to workaround it. You can define a static
route with recursive nex-hop like 192.0.2.x, and filter it out when it
is not reachable, but for any subprefix in /24 you would need to
define 256 of such
Hi,
Is is somehow possible to export a larger prefix if one or more sub-prefixes
(subnets) are exported ... but also remove that prefix if no smaller subnet
exist any more?
Example: As soon as 192.0.2.44/32 or 192.0.2.208/28 (or any other prefix inside
192.0.2.0/24) is exported via eBGP, also
11 matches
Mail list logo
