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
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
Hello Ray and list,
thank you for pointing at this. We actually intend to do kinda the
semantic versioning, we only didn't see any reason to add a trailing zero.
Regarding your case, I'd suggest to _not_ rely on the versioning being
x.y.z; what we can promise (and probably should document)
Hello bird users,
this is a short announcement that bird-2.14 is now available in a docker
container on https://hub.docker.com/r/ungleich/bird/tags .
As usual the image is based on the latest Alpine Linux version, this
time 3.19. Attached you find the latest Dockerfile in case you want to
In another context outside of this list, I was confused on the version
numbering as well, where I ran 2.0.x version, and someone else ran 2.y,
with y > x.
A small bit of digging revealed the following paragraph in the NEWS file
(see for example
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
>
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
