May 2025 - Bird-users - Mailing Lists

[BUG?] Segv with latest 3.1.1
by Nicolas Lorin 21 May '25

21 May '25

Hi, I've tried to upgrade from 3.1.0 to 3.1.1 but bird daemon is crashing with a segv after some seconds. I haven't made any change to my config. Reverting to 3.1.0 fixes the problem. Running Ubuntu 24.04.02. I'm using BGP/OSPF/Kernel/Static/Direct/RPKI. I haven't had the time yet to narrow the problem down but wanted to let you know. I'll try to investigate with a limited config if I find time. Regards, -- Nicolas Lorin

4 4

[BUG?] Unknown character on 3.1.0 and 3.1.1
by Tyrasuki 21 May '25

21 May '25

Hi there, I am experiencing bird throwing a <FATAL> Unknown character error on my configuration files. I suspect this might be related to CRLF vs LF, as all the positions it reports unknown character seems to be EOL or blank spaces. I should mention I am currently writing my configuration on a Windows machine, but it has passed between Linux and Windows a couple times. As an example, trying to start BIRD 3.1.0 on an Alpine Linux edge box gives the following: ns2:~# bird bird: 2025-05-20 18:39:55.659 [0001] <FATAL> /etc/bird.d/defines/constants.def:2:31 Unknown character ns2:~# head /etc/bird.d/defines/constants.def # Local preference values define LP_UPSTREAM = 100; define LP_PEER = 200; define LP_DOWNSTREAM = 300; define LP_OTHER = 150; # ASNs define AS_SELF = 209718; define AS_BOGON = [ 0, ns2:~# if I merge the second line with the first line to look like this: define LP_UPSTREAM = 100;define LP_PEER = 200; I get ns2:~# bird bird: 2025-05-20 18:41:02.547 [0001] <FATAL> /etc/bird.d/defines/constants.def:2:61 Unknown character Similarly, on another box running Debian 12 with the pkg.labs.nic.cz repository, on BIRD 3.1.1: bird3:~# bird bird: 2025-05-20 18:42:01.451 [0001] <FATAL> /etc/bird/bird.conf:1:26 Unknown character bird3:~# head /etc/bird/bird.conf router id 172.30.187.148; log "/var/log/bird.log" { error }; ipv6 table master6; ipv4 table master4; include "filters/netlist/*.list"; include "filters/AS.list"; include "define/*.def"; bird3~# Any suggestions would be welcome, as I am currently in the process of refractoring my routers from BIRD1 to BIRD3, and this has put me at a bit of a standstill. :) Kind regards, and thank you in advance for any response, Jori Vanneste / Tyrasuki

2 2

[2.16.1 on FreeBSD] Getting rid of a log message
by Elmar K. Bins 20 May '25

20 May '25

Hi everyone, I couldn't find anything in the docs, not much going on in terms of quenching log output. Also couldn't find any routecollector config examples that address this...so... I'm running this BIRD 2.16.1 (out of pkg/quarterly) as a routecollector, hence it does not need any next hops for anything. It is nicely telling me that "<neighbor-ip> resolvable through recursive route for <neighbor's-prefix>", which I don't want to know or see in my log - it's a huge load of entries . Is there a way to quench this log message, and/or is there a way to fine-tune log output in BIRD? Thanks, Elmar.

2 1

[PATCH] Build: call tools/version with sh
by xtexchooser＠duck.com 10 May '25

10 May '25

From: xtex <xtexchooser(a)duck.com> As tools/version has a shebang line, it should be fine to just call it without specifying bash. Calling bash explicitly may lead to inconsistency, as the first line of tools/version indicates /usr/bin/sh but the script is always executed with bash. And, it adds bash as a new build dependency. Signed-off-by: xtex <xtexchooser(a)duck.com> --- Please apply this to both 2.x and 3.x. Thank you! --- Makefile.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile.in b/Makefile.in index bbc1ef29da88..96a5b6eba60a 100644 --- a/Makefile.in +++ b/Makefile.in @@ -44,7 +44,7 @@ exedir := @exedir@ # Find out which version we are actually building # This is rewritten by the release tools by hardcoded version -VERSION := $(strip $(shell bash $(srcdir)/tools/version)) +VERSION := $(strip $(shell $(srcdir)/tools/version)) CFLAGS += -DBIRD_VERSION='"$(VERSION)"' base-commit: 7ef70b27ef907bba7479989a5376842c893b12bb -- 2.49.0

2 1

AES-256-GCM BGP Password Support?
by Anthony Hoppe 06 May '25

06 May '25

Hello! I am curious if BIRD has support for AES-256-GCM BGP passwords? Thanks! ~ Anthony -- This email, including its contents and any attachment(s), may contain confidential and/or proprietary information and is solely for the review and use of the intended recipient(s). If you have received this email in error, please notify the sender and permanently delete this email, its content, and any attachment(s). Any disclosure, copying, or taking of any action in reliance on an email received in error is strictly prohibited.

1 0

BIRD 2.17.1
by Ondrej Filip 05 May '25

05 May '25

Dear BIRD Users, we are releasing BIRD 2.17.1, fixing a BGP crash and NetBSD build. The BGP crash in question may happen when a client tries to connect to a disabled BGP protocol instance. This bug does NOT happen in BIRD 2.16.x and older, nor in BIRD 3.x. During this week, we repeatedly pushed and deleted the tag v42.42.42. This is a testing tag for our CI updates, please ignore it. We may use the same tag again to test CI behaviour on tags. Note: BIRD 2.17 and BIRD 3.1 have been included in Debian 13 Trixie and we expect these two versions to receive long term support for approx. next two years. Happy routing! Maria and Ondrej

1 0

How to use a variable for OSPF interfaces?
by Arnaud Gomes-do-Vale 02 May '25

02 May '25

Hi, I have a common block of configuration for a bunch of routers that I would like to share in an include file. It looks basically like this: ``` ipv6 table ospf_backbone6; protocol ospf v3 o_backbone_ipv6 { area 0 { interface "enp1s0f1.1004"; interface "loop0" { stub yes; }; }; ipv6 { import all; export all; table ospf_backbone6; }; } ``` The interface is different on every router and some routers have several (as in `interface "eth0.1004", "eth3";`), everything else is the same. I tried the obvious: ``` define OSPF_INTF = "enp1s0f1.1004"; protocol ospf v3 o_backbone_ipv6 { .../... interface OSPF_INTF; .../... } ``` Which BIRD definitely didn't like: ``` bird> conf check Reading configuration from /etc/bird/bird.conf /etc/bird/bird.conf:110:12 IP address or network constant expected ``` What did I miss? If this matters, this is with BIRD 2.0.12 from Debian bullseye backports. I can upgrade if needed but I don't want to if I don't have to. -- Arnaud

2 1

Assertion '!nacc && !nrej' failed at nest/rt-table.c:1532
by Matt Corallo 02 May '25

02 May '25

Figured I'd try bird 3.1.0 but sadly after increasing the threads to 6 (which made things settle fast!) I started hitting the above assertion sometimes. I don't have a core dump, but I may be able to get one if it happens again.

2 1