January 2025 - Bird-users

BIRD 3.0.1
by Ondrej Filip 13 Jan '25

13 Jan '25

Dear BIRD Users, let use share with you another announcement today, we are releasing version 3.0.1 of BIRD. We fixed quite some bugs there, as you could already have seen in the list. Most notably, we fixed crashes in dynamic BGP, graceful recovery, deterministic MED, BFD session reconfiguration and kernel path merging. We also fixed inefficiencies in feeds and refeeds and some heap bloating. Last but not least, we fixed the name of the bgp_otc route attribute. The packages are as always in our repository at https://pkg.labs.nic.cz/ and on our website at https://bird.network.cz/ Happy routing! Maria and Ondrej

2 1

porting the MPLS protocol to freebsd
by benoitc＠enki-multimedia.eu 13 Jan '25

13 Jan '25

Hi all, Did anyone tried to port the MPLS protocol to freebsd? What would need to be implemented to make it work? Any guidance is appreciated. Benoît

1 0

BIRD 2.16.1
by Ondrej Filip 11 Jan '25

11 Jan '25

Dear BIRD Users, we are releasing version 2.16.1 of BIRD. We fixed a parser bug in ASPA; the right keyword for aspa providers in static protocol is plural, i.e. providers, not provider as was wrongly enforced in some packages of 2.16. We also fixed crashes on certain ARM architectures due to bad memory alignment, and other minor bugs. The packages are as always in our repository at https://pkg.labs.nic.cz/ and on our website at https://bird.network.cz/ Happy routing! Maria and Ondrej

1 0

[bird graceful restart time] Is there any way to set graceful restart time?
by 이재용 10 Jan '25

10 Jan '25

Hello, We use BIRD for communication with servers with higher-level switches. In our config , there is config to set graceful restart like below. protocol bgp example2 {         import all;         export all;         ...         graceful restart on; } As far as I know, the default value for graceful restart is 120 seconds. But I don't know how to change this time. Please give me some advice on this. Thank you.

2 1

Customer ASN selection from ASPA tables
by Ralph Covelli 10 Jan '25

10 Jan '25

Hello Bird Team! I am able to load my static ASPA tables like normal into the new bird 2.16. bird> show route table at all Table at: 50555 [static1 2024-12-26] * (200) Type: static univ aspa_providers: 970 270470 [static1 2024-12-26] * (200) Type: static univ aspa_providers: 53062 47272 [static1 2024-12-26] * (200) Type: static univ aspa_providers: 174 835 924 1299 6830 6939 20473 21738 25759 34927 35133 41051 48605 50391 50917 52025 52210 58057 210667 212514 212895 However I am unable to select individuals or groups: bird> show route table at all where net.asn = 47272 Table at: bird> show route table at all where net.asn ~ [ 47272 ] Table at: bird> It looks like a spot was missed in filter/f-inst.c or it might have been left out intentionally because net.asn is already used for ROA's. filter/f-inst.c /* Get ROA ASN */ METHOD(T_NET, asn, 0, [[ if (!net_is_roa(v1.val.net)) runtime( "ROA expected" ); RESULT(T_INT, i, (v1.val.net->type == NET_ROA4) ? ((net_addr_roa4 *) v1.val.net)->asn : ((net_addr_roa6 *) v1.val.net)->asn); ]]); + /* Get ASPA ASN */ + METHOD(T_NET, customer_asn, 0, [[ + if (!net_is_aspa(v1.val.net)) + runtime( "ASPA expected" ); + + RESULT(T_INT, i, ((net_addr_aspa *) v1.val.net)->asn); + ]]); I named it customer_asn to avoid the collision but use whatever you want. Everything works great after the small correction: bird> show route table at all where net.customer_asn = 270470 Table at: 270470 [static1 19:05:34.388] * (200) Type: static univ aspa_providers: 53062 bird> show route table at all where net.customer_asn ~ [ 270470, 47272, 19330 ] Table at: 270470 [static1 19:05:34.388] * (200) Type: static univ aspa_providers: 53062 47272 [static1 19:05:34.388] * (200) Type: static univ aspa_providers: 174 835 924 1299 6830 6939 20473 21738 25759 34927 35133 41051 48605 50391 50917 52025 52210 58057 210667 212514 212895 19330 [static1 19:05:34.388] * (200) Type: static univ aspa_providers: 393577 bird> Thanks again for all of your hard work!

1 0

Concerning the structure of ASPA tables and AS0
by Ralph Covelli 09 Jan '25

09 Jan '25

Hello Bird Team! My name is Ralph. I'm a network engineer and C programmer for Hurricane Electric. I am a long time fan of the Bird project! Keep up the great work!! Earlier this year I was tasked with implementing reactive ASPA in our network. My code was based off your older implementation of static ASPA tables here: https://gitlab.nic.cz/labs/bird/-/tree/aspa This older implementation is based off of customer-provider pairs: typedef struct net_addr_aspa { u8 type; u8 padding; u16 length; u32 customer_asn; u32 provider_asn; } net_addr_aspa; I've attached the patch as "bird-2.15.1-aspa-asn-pairs.patch". I took a look at 2.16 and ran into 2 problems. Respectfully, I would like to report two issues with the ASPA code in 2.16. Issue #1) There is no way to tell the difference between a transit entry and an "AS0" entry. $ cat bird-aspa.conf aspa table at; protocol static { aspa; route aspa 12345 transit; route aspa 970 provider 43, 56; route aspa 43970 provider 0; } --- $ ./sbin/birdc BIRD 2.16 ready. bird> show route table at all Table at: 43970 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 970 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 43 56 12345 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 bird> --- The treatment of AS0 providers is mentioned in section 5 of draft-ietf-sidrops-aspa-verification-19. It is a mechanism for people to announce that "no one should announce this AS". I've attached a snapshot of the global ASPA table as "bird-aspa-v2.16.conf". There is one AS0 announcement as of today. Issue #2) Changes in static ASPA tables are not reflected until entries are removed and re-added. $ cat bird-aspa.conf aspa table at; protocol static { aspa; route aspa 12345 transit; route aspa 970 provider 43, 56; route aspa 43970 provider 0; } bird> show route table at all Table at: 43970 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 970 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 43 56 12345 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 bird> $ cat bird-aspa.conf aspa table at; protocol static { aspa; route aspa 12345 transit; route aspa 970 provider 43, 56, 78; <---- added AS78 route aspa 43970 provider 0; } $ ./sbin/birdc BIRD 2.16 ready. bird> configure Reading configuration from /home/rpki/bird/etc/bird.conf Reconfigured bird> show route table at all Table at: 43970 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 970 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 43 56 <-------- changes not reflected *** 12345 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 bird> $ cat bird-aspa.conf aspa table at; protocol static { aspa; route aspa 12345 transit; #route aspa 970 provider 43, 56, 78; <----- remove entries altogether route aspa 43970 provider 0; } $ ./sbin/birdc BIRD 2.16 ready. bird> configure Reading configuration from /home/rpki/bird/etc/bird.conf Reconfigured bird> show route table at all Table at: 43970 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 12345 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 bird> $ cat bird-aspa.conf aspa table at; protocol static { aspa; route aspa 12345 transit; route aspa 970 provider 43, 56, 78; <------- add entry again route aspa 43970 provider 0; } $ ./sbin/birdc BIRD 2.16 ready. bird> configure Reading configuration from /home/rpki/bird/etc/bird.conf Reconfigured bird> show route table at all Table at: 43970 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 970 [static1 20:17:30.142] * (200) Type: static univ aspa_providers: 43 56 78 <--------- changes reflected correctly 12345 [static1 19:38:32.125] * (200) Type: static univ aspa_providers: 0 bird> --- This problem does not occur when the ASPA elements are customer-provider pairs. I believe this is an overall design issue, not a simple bug. I will be bringing this issue up with ietf-sidrops. Thanks! -- Ralph Covelli Hurricane Electric / AS6939 Network Engineer

2 8

Bird on Ubuntu VM.
by Mike Neo 09 Jan '25

09 Jan '25

Hi, I currently have 2 servers Dell R310 with Bird 1.6 on Ubuntu (Active/Passive), one full BGP table and one IX, traffic around 400Mbps, simple BGP routing. I also have an HA cluster built on ESXi and I wonder if it would be a good idea to run BIRD (maybe 2.0/3.0?) on a VM (Ubuntu) on this ESXi HA cluster. What are your experiences with this, what are the limitations and recommendations? Kind Regards, Mike

3 4

annoying log, received route with strange next hop, Netlink File exists
by LIU Chris 08 Jan '25

08 Jan '25

Classified as: {Hitachi Rail - Public} Basically configured bird as below protocol device { scan time 10; } protocol kernel { scan time 10; learn; ipv4 { export filter XXXX; } } bgp and bfd are established, everything is fine. But only have some annoying log: Every 10 seconds to print below bird log, assuming this is caused by kernel protocol scan time 10. But why Netlink : File exists, it would write to kernel ??? KRT: Received route xx.yy.zz.0/24 with strange next-hop 10.0.0.1 Netlink: File exists Chris {Hitachi Rail - Public}

2 2

first (?) bird 3.0.0 bug report
by Radu Anghel 08 Jan '25

08 Jan '25

Hi, Using a slightly modified version of the config from the 2.15.1 (just some {} inside case structures), but probably unrelated. If bird gets killed/not shut down properly and routes remain in the kernel then bird 3.0.0 is unable to restart and just segfaults when trying to refresh kernel routes. I can reproduce it by just kill -9 bird && restarting bird. daemon.debug bird: KERNEL6.ipv6: route refresh begin: rr 1 set 1 valid 0 pruning 0 pruned 0 kern.info kernel: [75645.964935] bird[4162]: segfault at 0 ip 000000000045d47b sp 00007ffcb9f9f2c0 error 4 in bird[403000+a8000] likely on CPU 1 (core 0, socket 1) kern.info kernel: [75645.970115] Code: 5d 41 5c 41 5d 41 5e 41 5f c3 55 53 48 89 fb 48 83 ec 38 80 bb 79 02 00 00 04 48 8b 7f 30 75 46 48 89 d5 31 d2 e8 63 a4 ff ff <83> 38 00 49 89 c0 75 07 31 c0 e9 9d 00 00 00 48 8b 40 10 48 8d 7b The kernel protocol config is: protocol kernel KERNEL6 { debug { events, states }; scan time 3600; merge paths on; metric 0; ipv6 { import filter KERNEL_IN; export filter KERNEL_OUT; }; } Cheers, R

4 11

Bird 2.16 ASPA issue
by Jelle Luteijn 08 Jan '25

08 Jan '25

Hoi, Yesterday I tried to implement the validation of ASPA in my router filters. I have generated the ASPA table via the mainline version of RPKI-Client, docker image rpki/rpki-client:edge to be precise. For Bird I use version 2.16 provided from https://pkg.labs.nic.cz/. When loading the bird configuration with the new table I get the following error: /etc/bird/rpki2/bird:642145:17 syntax error, unexpected PROVIDERS this line is: route aspa 945 providers 174, 6461, 6939, 7018, 9002, 32097, 401111; (full table provided below) I tested this yesterday with Job Snijders. He told me that when bird 2.16 is compiled from source it does work, and he was able to replicate the issue with the packages from the repository. I prefer not to compile the software myself and to use vendor provided packages. Does somebody know what’s going on? Regards, Jelle Luteijn --- define force_roa_table_update = 1736147917; aspa table ASPAS; #ROAs are removed from snippet due to size protocol static { aspa { table ASPAS; }; route aspa 945 providers 174, 6461, 6939, 7018, 9002, 32097, 401111; route aspa 970 providers 54874; route aspa 11358 providers 835, 924, 6939, 20473, 34927; route aspa 13852 providers 6939, 20473, 34927, 52025, 209533; route aspa 15562 providers 2914, 8283, 51088, 206238; route aspa 16909 providers 20473, 21738, 34927, 47272, 53356, 53667, 152900, 209643, 212477; route aspa 19330 providers 393577; route aspa 21957 providers 970; route aspa 28584 providers 28605; route aspa 33733 providers 174, 6939, 12186, 47787, 200454; route aspa 40544 providers 924, 6939, 12186, 52025; route aspa 41720 providers 174, 1299, 9002, 50877, 60068, 203446, 212508; route aspa 44324 providers 945, 955, 1299, 3204, 6939, 7720, 8772, 8849, 15353, 18041, 20473, 29632, 32595, 34465, 34927, 41051, 43426, 47272, 48266, 51087, 53667, 53808, 59105, 59538, 61112, 134823, 134835, 138997, 139317, 150452, 151364, 199545, 199765, 200105, 206499, 207656, 207841, 209554, 209735, 212483, 213856; route aspa 44355 providers 207841; route aspa 47272 providers 174, 835, 924, 1299, 6830, 6939, 20473, 21738, 25759, 34927, 35133, 41051, 48605, 50391, 50917, 52025, 52210, 58057, 210667, 212514, 212895; route aspa 47689 providers 924, 1299, 6939, 21738, 34465, 34549, 34927, 395823; route aspa 48070 providers 174, 1299; route aspa 48606 providers 30893, 54681, 57974, 59678, 210691, 212276; route aspa 50224 providers 6939, 15353, 26930, 34465, 37988, 50104, 52025, 52210, 59920, 60841, 210475, 400304; route aspa 50391 providers 6939, 20473, 48070; route aspa 50555 providers 970; route aspa 51019 providers 6939, 34549, 34927, 52025, 207841; route aspa 51396 providers 6939, 30823, 35133, 44066, 44592, 49581, 60223, 64457, 203446, 214497, 214995, 215436; route aspa 52025 providers 174, 835, 906, 917, 924, 1299, 3257, 6204, 6939, 7720, 8860, 12186, 18041, 20473, 21700, 21738, 25369, 29802, 32097, 34549, 34927, 35133, 35661, 36369, 37988, 39409, 47787, 48070, 48605, 50917, 51519, 52210, 56655, 57695, 61138, 64289, 197216, 199545, 208453, 209022, 209533, 394177, 396998, 397423, 400304, 400587; route aspa 52210 providers 174, 835, 6939, 52025, 62513, 210667; route aspa 54148 providers 835, 924, 6939, 20473, 21738, 34927, 37988, 47272, 50917, 53616, 53667, 207841, 209022, 209735; route aspa 54218 providers 917, 16509, 35487, 37988, 53667, 57196, 59678; route aspa 56762 providers 47689; route aspa 57984 providers 8283, 48112, 206763; route aspa 59678 providers 6939, 34927, 54218, 55081; route aspa 60223 providers 945, 49581; route aspa 60431 providers 34927, 41495, 50917; route aspa 60841 providers 30456, 400304; route aspa 149301 providers 20473, 61138; route aspa 151642 providers 20473, 61138; route aspa 198136 providers 0; route aspa 199310 providers 44324, 134835, 138997, 139317, 202662, 204844, 212895, 215828; route aspa 199376 providers 47311, 61112, 150249, 151544, 199762, 209533, 215379; route aspa 199762 providers 945, 6939, 8849, 15353, 34927, 44817, 47311, 48605, 140731, 150249; route aspa 200242 providers 835, 6939, 21738, 34465, 34927, 52025, 52041, 59678, 60841, 208453, 210475; route aspa 200351 providers 34927, 47272, 209022, 210475; route aspa 200454 providers 174, 6424, 6939, 9186, 12186; route aspa 202076 providers 207960; route aspa 202359 providers 30740, 33920, 41495; route aspa 202881 providers 205329; route aspa 203236 providers 20473, 44324, 53667, 53808, 200105, 201217, 203314, 213856; route aspa 203619 providers 200454; route aspa 203843 providers 6939, 20473, 53667; route aspa 204857 providers 50224, 59920, 60841, 400304; route aspa 204931 providers 34927, 44103, 207656; route aspa 205329 providers 945, 983, 6939, 7720, 8894, 9409, 20473, 34927, 41051, 131657, 134823, 151364; route aspa 205603 providers 38008, 38074, 59105; route aspa 205663 providers 20473, 61138; route aspa 205789 providers 200242, 207960; route aspa 205848 providers 1299, 6939, 34549, 34927, 52025, 209022; route aspa 207487 providers 20473; route aspa 207841 providers 6939, 137409; route aspa 207960 providers 6939, 20473, 34854, 34927, 136620, 202359, 207968; route aspa 209735 providers 6939, 207841; route aspa 210561 providers 207960; route aspa 212068 providers 6939, 13237, 62240, 207960; route aspa 212245 providers 917, 57695, 212068; route aspa 212516 providers 3204, 6939, 41720; route aspa 212934 providers 835, 6939, 34927, 52210, 53667, 61138, 62513, 209533, 210667; route aspa 213915 providers 215147, 215828; route aspa 214498 providers 16276, 207841; route aspa 215085 providers 35133, 42093, 52025; route aspa 215131 providers 8283, 34927, 212477; route aspa 215147 providers 34927, 41108, 47263, 207252, 213915, 215828; route aspa 215368 providers 207841; route aspa 215436 providers 6762, 6939, 51396, 60223; route aspa 215664 providers 1299, 3204, 6939, 34549, 41720, 56382, 203446, 212508; route aspa 215778 providers 8772, 29632, 39249, 41051, 207656, 209533; route aspa 215828 providers 6204, 6939, 8772, 29390, 29632, 34465, 34927, 39249, 41051, 44592, 48752, 50917, 51019, 51202, 58057, 62403, 152726, 197071, 199524, 203686, 207656, 209533, 210464, 211358, 215147, 216324, 216360, 393577; route aspa 215849 providers 215828; route aspa 216107 providers 924, 6939, 16509, 20473, 21738, 34927, 63473, 209022, 211588; route aspa 216265 providers 202673, 215051; route aspa 216311 providers 6939, 13852, 20473, 34927, 52025; route aspa 267386 providers 6939, 25933, 28220, 28649, 267613; route aspa 270470 providers 53062; route aspa 393577 providers 1299, 6939, 32097, 40676, 137409; route aspa 401111 providers 1012, 2497, 17676; route aspa 401507 providers 53356, 212477; }

4 8