May 2025 - Bird-users - Mailing Lists

BIRD 3.1.0, 2.17, 3.0.2, 2.16.2 released
by Ondrej Filip 24 Aug '25

24 Aug '25

Dear BIRD Users, we have released four versions of BIRD at once; 2.17 and 3.1.0 with new features and 2.16.2 and 3.0.2 fixing bugs in 2.16.1 and 3.0.1, respectively. It may become common in the future to keep certain versions stable with only fixes for some longer time. Specifically, 3.1.0 and 2.17 have already successfully migrated to Debian testing, so these versions may get quite a long chain of updates. In 2.17 and 3.1.0, we added TCP-AO support for BGP on Linux. We haven't found any resource for TCP-AO in any flavor of BSD; if you know of any, please tell us. We also implemented graceful restart timer minima and maxima in BGP, format specification for link-local-only next hops in BGP, to improve compatibility with other routing stacks, and also we merged a new next hop option for IPv4 routes in Babel. In 3.1.0, we also added a compatibility layer for show route outputs, to allow your BIRD 2 automation to work with BIRD 3. Please tell us if you find any significant difference there. In all versions, we fixed several rare crashes in BFD and table removal, and other minor bugs. In 3.1.0 and 3.0.2, we also fixed quite some crashes in route propagation and state machines. Also setting route gateway in 3.x by filters is now fixed. It also looks like that some bugs in 3.1.0 slipped through our release process, most notably failure to build on FreeBSD 13 with Netlink and some strange crash on BGP neighbor flap. We are currently investigating that and we may release 3.1.1 soon. We apologize for for that. Anyway, the packages are as always in our repository at https://pkg.labs.nic.cz/ and on our website at https://bird.network.cz/ Have a pleasant spring or autumn, and happy routing! Ondrej and Maria

6 5

Crash width Assertion '!rejected || !accepted' failed at nest/rt-table.c:1192
by Alexey Boldyrev 02 Jun '25

02 Jun '25

Backtrace: Apr 26 18:05:26 router bird[751]: Netlink: Invalid argument Apr 26 18:05:26 router bird[751]: Netlink: Invalid argument Apr 26 18:05:26 router bird[751]: ... Apr 27 02:09:23 router bird[751]: AS4200220008: Error: Hold timer expired Apr 27 02:10:59 router bird[751]: AS4200220008: Error: Hold timer expired Apr 27 13:14:03 router bird[751]: Assertion '!rejected || !accepted' failed at nest/rt-table.c:1192 Apr 27 13:14:03 router systemd-coredump[1345547]: [🡕] Process 751 (bird) of user 967 dumped core. Stack trace of thread 824: #0 0x0000777b9f380624 n/a (libc.so.6 + 0x97624) #1 0x0000777b9f326ba0 raise (libc.so.6 + 0x3dba0) #2 0x0000777b9f30e582 abort (libc.so.6 + 0x25582) #3 0x000065083a2cb01f n/a (/usr/bin/bird + 0xe001f) #4 0x000065083a248712 n/a (/usr/bin/bird + 0x5d712) #5 0x000065083a249117 n/a (/usr/bin/bird + 0x5e117) #6 0x000065083a21d0cf n/a (/usr/bin/bird + 0x320cf) #7 0x000065083a2cf838 n/a (/usr/bin/bird + 0xe4838) #8 0x000065083a21d0cf n/a (/usr/bin/bird + 0x320cf) #9 0x000065083a2d1ee7 n/a (/usr/bin/bird + 0xe6ee7) #10 0x0000777b9f37e708 n/a (libc.so.6 + 0x95708) #11 0x0000777b9f402aac n/a (libc.so.6 + 0x119aac) Stack trace of thread 751: #0 0x0000777b9f386be2 n/a (libc.so.6 + 0x9dbe2) #1 0x0000777b9f37ae33 n/a (libc.so.6 + 0x91e33) #2 0x0000777b9f37ae74 n/a (libc.so.6 + 0x91e74) #3 0x0000777b9f3f553e __poll (libc.so.6 + 0x10c53e) #4 0x000065083a1f1a14 n/a (/usr/bin/bird + 0x6a14) #5 0x0000777b9f310488 n/a (libc.so.6 + 0x27488) #6 0x0000777b9f31054c __libc_start_main (libc.so.6 + 0x2754c) #7 0x000065083a1f2565 n/a (/usr/bin/bird + 0x7565) Stack trace of thread 826: #0 0x0000777b9f386be2 n/a (libc.so.6 + 0x9dbe2) #1 0x0000777b9f37ae33 n/a (libc.so.6 + 0x91e33) #2 0x0000777b9f37ae74 n/a (libc.so.6 + 0x91e74) #3 0x0000777b9f3f553e __poll (libc.so.6 + 0x10c53e) #4 0x000065083a2d2020 n/a (/usr/bin/bird + 0xe7020) #5 0x0000777b9f37e708 n/a (libc.so.6 + 0x95708) #6 0x0000777b9f402aac n/a (libc.so.6 + 0x119aac) ELF object binary architecture: AMD x86-64 Apr 27 13:14:03 router systemd[1]: bird.service: Main process exited, code=dumped, status=6/ABRT Apr 27 13:14:03 router systemd[1]: bird.service: Failed with result 'core-dump'. Apr 27 13:14:03 router systemd[1]: bird.service: Consumed 3min 7.732s CPU time, 6.1M memory peak. Version: 3.1.0

4 3

BIRD performance in a dynamic scenario
by Maxime Peim (mpeim) 01 Jun '25

01 Jun '25

Hi everyone, First of all, thanks a lot for BIRD ! I have some questions about the dynamicity of BIRD wiht BGP. In a scenario where routes needs to be updated accondingly depending on some external informations, I find out that those informations would need to be written into the BIRD configuration file. As an example, if we need to add a bgp community based on the peer address (already known), we would need something like that : ```bird function get_community_from_peer_address(ip addr) -> pair { case addr { <addr1> : (1,1) ; <addr2> : (245, 12434) ; … else : (0, 0) ; } } ``` And we could update that function if needed in the future but the configuration will need to be parsed each time. If the rate of update is high, it can become a bootleneck. So I would like to know if I am going the right direction doing that way ? Is there a plan for a direct API to BIRD internals instead of passing a configuration file ? Thanks in advance for your answer, Maxime Peim

2 6

BIRD 3.1.1 and 3.0.3 released
by Maria Matejka 29 May '25

29 May '25

Dear BIRD users, we are releasing BIRD versions 3.1.1 and 3.0.3. We have fixed BGP route refresh in both versions, and also several build issues on FreeBSD, NetBSD, and CentOS 7. We added several table export fixes to 3.1.1 which were already included in 3.0.2. We fixed several other minor bugs and rare crashes as well. Release tarballs are available on our website <https://bird.nic.cz/get-bird>. Debian and Ubuntu packages are available in our repository at <https://pkg.labs.nic.cz/doc?project=bird>. You may have noticed that the person tagging the version and sending this e-mail has changed. There is also a change in the website URL. I'll send a full e-mail summarizing the organizational changes during the next week. Happy routing! Maria, with Ondrej's approval -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.

5 10

handling of the onlink next hop
by Radu CARPA 28 May '25

28 May '25

Hi team, We've just got the update of bird (bird-2.16.2-1.el9.x86_64->bird-3.1.1-1.el9.x86_64) delivered via rpm updates and it broke our configuration with the following error message: `/etc/bird.conf:7:5 syntax error, unexpected ONLINK` By reading the migration guide, i see that it was a deliberate choice to stop supporting this attribute: "The|onlink|route attribute has been temporarily disabled until we find out how to implement it properly." We used the functionality implemented in 7144c9ca46f092da33a4e051bbce8f973a3bd8c4 . In particular, with the following configuration: ``` ifname = "tunl0"; onlink = true; gw = from; ``` Is there a plan to bring back support for it in the nearby future? If not, I will try to get in touch with the maintainer of the package in EPEL to see if it's possible to submit and keep maintaining a "bird2" branch of this package in EPEL. Regards, Radu

3 7

BIRD 3.1.2 and 3.0.4 released
by Maria Matejka 28 May '25

28 May '25

Dear BIRD users, we are releasing BIRD versions 3.1.2 and 3.0.4. We have fixed several crashes in table exports, broken ASPA checks, a crash in MRT, and a logging bug in configure undo. Packages are available on our website <https://bird.nic.cz/get-bird>. Debian and Ubuntu packages are available in our repository at <https://pkg.labs.nic.cz/doc?project=bird>. Also, I have promised an organizational update to you, and I haven't done it yet. We were working hard on fixing all of these reported regressions, so this went a bit aside. Sorry for that, gonna do it very very soon. Thanks to the whole team for fixing and testing! Happy routing! Maria and the BIRD Team -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.

1 0

Interaction of OSPFv2 and PtP tunnels (bug?)
by LEdoian 27 May '25

27 May '25

Hello! I seem to have hit a strange inconsistency when OSPFv2 does not create routes for its PtP transit interfaces and am not sure whether I am misunderstanding the protocol. I managed to reduce my case into the following setup (full Linux netns reproducer script is at the end): There are three machines, called Local, Remote and Foreign and OSPFv2 running among them. Local is the middle one, having a virtual ethernet to Foreign (IP addresses 10.2.0.0/24) and a 4in6 tunnel to Remote (10.1.0.1 and 10.1.0.2). Moreover, the Local and Remote machines have a dummy interface with another local address (10.0.0.1, 10.0.0.2). In this case, OSPF converges, but the routing tables on Local and Remote are missing the route for 10.1.0.0/30: ``` Table master4: 10.2.0.0/24 unicast [ospf1 03:24:08.362] * I (10/100) [0.0.0.3] dev en_f 10.0.0.1/32 unicast [ospf1 03:23:27.361] * I (10/0) [0.0.0.1] dev dummy0 10.0.0.2/32 unicast [ospf1 03:23:43.363] * I (10/100) [0.0.0.2] via 10.1.0.2 on tun0 ``` OSPF is about the 10.1.0.0/30 addresses, breaking connection between Foreign and Remote. Surprisingly, if the tunnel interface is marked as stub, then the route is imported in the same manner as the route on the veth (but the toy network now has two independent instances of OSPF, effectively being split). The missing route can be added by enabling the Direct protocols but this feels quite off, as the route should not be external to OSPF. Also, the Direct protocol documentation suggests that this should not be necessary: “OSPF protocol creates device routes for its interfaces itself […]”. My reproducer runs on Arch Linux with BIRD 3.1.1, but also appears on my router running BIRD 2.13.1. Am I misunderstanding something, or is this actually a bug? Best regards, LEdoian --- #!/bin/bash # intended to be run inside `unshare -rnmpf --mount-proc` # uses tmux to keep sessions and to run BIRDs in background set -e dir="$(mktemp -d)" mount -t tmpfs bird-repro "$dir" trap 'cd / && umount --recursive "$dir" && rmdir "$dir"' EXIT # does not work cd "$dir" cat >bird.inc <<GO log stderr all; debug protocols all; protocol device { } protocol direct{ ipv4; disabled; } protocol kernel ker4 { learn; ipv4 { preference 100; import all; export all; }; } protocol ospf v2 { ipv4 { preference 10; import all; export all; }; area 0 { interface "tun*" { cost 100; #stub; }; interface "dummy*" { cost 100; stub; }; interface "en*" { cost 100; }; }; } GO cat >local.conf <<GO router id 0.0.0.1; include "bird.inc"; GO cat >remote.conf <<GO router id 0.0.0.2; include "bird.inc"; GO cat >foreign.conf <<GO router id 0.0.0.3; include "bird.inc"; GO for x in remote local; do touch $x unshare --net=$x ip link add dummy0 type dummy nsenter --net=$x ip link set dummy0 up done nsenter --net=local ip addr add 10.0.0.1/32 dev dummy0 nsenter --net=remote ip addr add 10.0.0.2/32 dev dummy0 ip link add name ve0 type veth peer ve1 ip link set ve0 netns ./local ip link set ve1 name ve0 ip link set ve0 netns ./remote nsenter --net=local ip addr add fd00::1/64 dev ve0 nsenter --net=remote ip addr add fd00::2/64 dev ve0 nsenter --net=local ip link set ve0 up nsenter --net=remote ip link set ve0 up nsenter --net=local ip link add tun0 type ip6tnl mode ipip6 local fd00::1 remote fd00::2 nsenter --net=local ip link set tun0 up nsenter --net=local ip addr add 10.1.0.1 dev tun0 peer 10.1.0.2 nsenter --net=remote ip link add tun0 type ip6tnl mode ipip6 local fd00::2 remote fd00::1 nsenter --net=remote ip link set tun0 up nsenter --net=remote ip addr add 10.1.0.2 dev tun0 peer 10.1.0.1 touch foreign unshare --net=foreign true ip link add name en_f type veth peer en_l ip link set en_f netns ./local ip link set en_l netns ./foreign nsenter --net=foreign ip link set en_l up nsenter --net=foreign ip addr add 10.2.0.3/24 dev en_l nsenter --net=local ip link set en_f up nsenter --net=local ip addr add 10.2.0.2/24 dev en_f nsenter --net=local sysctl net.ipv4.conf.all.forwarding=1 for x in local remote foreign; do nsenter --net=$x tmux -S $x.tmux new-session -d bird -d -c $x.conf -s $x.bird done tmux

2 1

Issues running BMP protocol in v3.0.1
by admin＠nxthdr.dev 26 May '25

26 May '25

Hey, I've migrated from 2.16.1 to 3.0.1 and I'm facing some issues with the BMP protocol. The TCP session goes up but I don't receive all peers up notifications. I receive some (but not all it seems) when I restart bird after have started my BMP collector. If I do the opposite, I get none. Also, I don't receive route monitoring messages. To be precise, I receive only one route monitoring message when I receive a peer up notification. But this one is empty (meaning no announced/withdrawn prefixes in it). Also I receive it just just before the peer up, which is a bit weird. I should receive a tons of them, with announced prefixes in it, right after the peer up. Here is my BMP configuration: protocol bmp { station address ip 2a06:de00:50:cafe:100::c port 4000; monitoring rib in pre_policy; monitoring rib in post_policy;} bird> show protocols all bmp1 Name Proto Table State Since Info bmp1 BMP --- up 18:08:26.528 Established Created: 18:08:16.105 Station address: 2a06:de00:50:cafe:100::c Station port: 4000 Pending TX: 0 B (limit 1024.0 MB) Session TX: 789 B Total TX: 789 B Do you experience the same behavior? Please let me know if you need more information, I'm happy to make some other tests if needed. Best,Matthieu.

1 1

<ERR> filters, line 1: Missing AS_PATH attribute
by ushiroz＠ate-mahoroba.jp 23 May '25

23 May '25

Hi, In our BIRD 2.14 we’re running roa_check like this: if (net.type = NET_IP4) then { case roa_check(r4, net, bgp_path.last) { However, the BIRD logs show the following error: <ERR> filters, line 1: Missing AS_PATH attribute would it be advisable to add a check to determine whether the route is a BGP route before proceeding?

2 2

[2.16.1 on FreeBSD] Automatic RPKI reload not active...
by Elmar K. Bins 21 May '25

21 May '25

Hi folks, again, In my logs, I'm seeing a lot of <peer>: Automatic RPKI reload not active for import I could not find any explanation what that would mean, or whether it is a problem... Can somebody help? Thanks, Elmar.

3 10