April 2024 - Bird-users - Mailing Lists

Problem with uplink network announcment in IPv6
by Yasen Atanasov 02 Apr '24

02 Apr '24

Hello, I've experienced a strange problem when implementing IPv6 connectivity. My ISP gave me /126 for connection between bgp routers and uplink connectivity. A lot of(but not all) routes couldn't be inserted in the kernel. After some experimentation we realized that administrative route that is created buy the kernel for local networks was overridden by the bird and after that no new routes were inserted in the kernel table. ~# ip r get x::y x::y from :: via x::y dev eth6 proto bird src x::z metric 32 pref medium vs x::y from :: dev eth6 proto kernel src x::z metric 256 pref medium Where x::y is uplink BGP peer and x::z our BGP router. Filtering /126 network from imports resolved the problem Is this normal behavior for Bird or some misconfiguration from our side? Should I report that as misconfiguration to my ISP? I'm using bid 2.0.12 from Devuan 5 repos. Any input will appreciated. Yasen

2 1

Coexistence of multiple babel daemons on the same host
by Daniel Gröber 02 Apr '24

02 Apr '24

Hi Babelers, I've just come across a reason I'd want to run babel with both bird and babeld on the same node and have them become neighbours. The details are tedious -- my usual disclamer applies ;) This got me to think about something I'd observed in the past and been meaning to write about though: when I accidentally had both babeld and bird running on a node it would casuse severe route flapping and consequently packet loss. I wonder if we can do better here? Maybe by warning about this situation in the logs, shutting down both sides or just turning this into a supported use-case? :) >From what I gather by a quick skimming of the relevant details in RFC8966 this could work by assigning each daemon a unique LL address so each gets it's own entry in the neighbour table, right? Thanks, --Daniel

3 4

How to make bird and freebsd carp working together ?
by Arnaud Houdelette-Langlois 01 Apr '24

01 Apr '24

Hi I got two routers running freebsd (BSDRP). Those two are used as redundant site firewalls and main routers / route servers. Both exchange routes between themselves and other routers using Bird (OSPF+BGP). Both serve as gateway for our management network, with carp enabled. I got trouble making CARP and BIRD working together. The carp enabled interface use a dummy network for exchanging carp info (link local adresses : 169.254.1.0/24) Bird Device protocol does not makes any difference between adresses in MASTER or BACKUP vhids, so the route appears in both routers. I tried with recent "learn all" feature of kernel protocol : There, bird only picks up route when its master, but, in case of MASTER failover or preemption, it doesn't remove the route early enough, and freebsd does not seem to replace the route on it’s kernel table, so when birds finally removes the route, we end up with no route at all. (and a non working network segment). Am I the only one facing this issue ? Is there a way to make bird carp aware ? Thanks -- Arnaud Houdelette-Langlois Administrateur des infrastructures systèmes et réseaux Normandie Université

2 1