Hello everyone,
I was wondering how you typically handle announcing
a decentralised infrastructure to its upstreams / the Internet and how
you handle receiving your own routes again on other upstreams.
The scenario is as follows:
CUSTOMER
PEERINGS 1 -- AS P6 --- CUSTOMER PEERINGS 2
|
Hello!
Thank you for confirming that Calico still runs BIRD 1.6… and also it's nice to
know that it's not our bug.
Happy holidays!
Maria
On 26 December 2023 11:27:24 CET, Nico Schottelius via Bird-users
wrote:
>
>And again. So this is my Christmas present of stupidity to everyone out
>there
And again. So this is my Christmas present of stupidity to everyone out
there - I hope you are not running into the same issue ever in your
life.
If you do, you might be as stupid as me and have a misplaced calico CNI
installed on the same node that happens to have a BGP configuration
without
Good morning,
yesterday we upgrade in a lab from 2.13.1 to 2.14 and (great idea) at
the same time modified some configuration bits. Since then bird does not
seem to write routes into the kernel anymore, even though relevant bits
seem to be in the configuration.
The config (in parts) looks like
Hello all,
I have been using Bird1 series + Alice + birdwatcher configuration as ULG.
With Bird2 series, since Bird does not separate processes by IPv4 and IPv6,
will it be impossible to separate the display method in Alice by IPv4 and
IPv6?
I changed the birdwatcher to the Docker one that is
Hello again,
I was just able to reproduce the route injection and vanishing by
restarting bird. The following ip -6 r commands have been taken while
bird was running within 10 seconds of the start of bird:
[10:16]