Hi all, I'm the Calico engineer closest to the BIRDv1 usage situation here. We entirely understand that v1 is now end-of-life and that we should use v2 or v3 instead. We'd also prefer to use a fully upstream BIRD instead of our own fork.

The plan for that is in place, but will still take a little while to work through. We only created our own fork because we needed some tweaks for IP-IP route programming; but we just deprecated the use case that requires that, in Calico v3.33, and support will be removed in Calico v3.35, and then we will be free to switch to an upstream v2 or v3 (and intend to do that).

Until that plays out, we will still consider any issues or PRs for our v1 fork; please direct those to https://github.com/projectcalico/bird.

Best wishes - Nell

On Thu, Oct 8, 2026 at 11:49 AM David Petera via Bird-users <bird-users@network.cz> wrote:

Hi,

if I can see correctly Calico is still using BIRDv1 that they keep alive themselves...

Since last version of BIRDv1 was released in 2019 (so 7 years ago) and it was subsequently made end-of-life in 2023, we do not upstream any fixes to that version anymore.
In fact we really advise against using BIRDv1 in any serious operation.

Any issues with BIRDv1 should be resolved by upgrading to BIRDv3 or BIRDv2. In case the issue persists, report it to us then, and we will be more than happy to fix it in our supported versions.

Supporting three versions at the same time is above current capacities of our team.

Hope this helps,
David
David Petera (he/him) | BIRD Tech Support | CZ.NIC, z.s.p.o.
On 10/6/26 17:16, Юрий Иванов wrote:

Hi,

We faced the same problem discussed here https://github.com/projectcalico/bird/issues/95

According to the message https://github.com/projectcalico/bird/issues/95#issuecomment-2373663908 this bug should be fixed.

Still can't find whether these patches was included into main branch.