August 2019 - Bird-users

Support for setting Aggregator IP/ASN in BGP Updates
by Clemens Mosig 19 Aug '19

19 Aug '19

Hi all, we are manually announcing and withdrawing prefixes by disabling and enabling a static protocol: E.g: protocol static prefix{ ipv4; route 1.2.3.0/24 blackhole; } Is there a way to manually set the BGP AGGREGATOR IP address or ASN for the resulting announcements or withdraws? Cheers, Clemens

2 1

iBGP problem with full meshed routers
by Martin Bosner 19 Aug '19

19 Aug '19

Hello, i'm a little desperate and helpless because i can't get any further with my current problem: My current setup (all same AS only physical): router A ---- router B --- router C ------- router E --- router G (has full \ | | | table uplink) \ | | | \ | | | router D ------- router F --- router H Router ABCD and router EFGH are each at the same location in a L2 network. There are no additional static routing information but the one from the interfaces and they are all connected via BGP using the same AS. All routers can ping each other and no router has a default gw. All BGP sessions are using the same table and are up and alive. All direct connected routers have a "direct" connection and all non direct connected routers use multihop. The problem is that router G and router H only have invalid global routes learned from router A while E and F are fine: (using 223.230.128.0/22 is just a random pick for demonstration) router G and H (PROBLEM): BIRD SHOW ROUTE birdc show route 223.230.128.0/22 all BIRD 2.0.5 ready. Table master4: 223.230.128.0/22 unreachable [routerG_to_routerA 03:15:02.410 from 153.92.124.4] * (100/-) [AS45609?] Type: BGP univ BGP.origin: Incomplete BGP.as_path: 15943 9498 45609 BGP.next_hop: 153.92.124.4 BGP.local_pref: 100 KERNEL route -n | grep 223.230.128.0 223.230.128.0 - 255.255.252.0 ! 32 - 0 - CONFIG protocol bgp routerG_to_routerA{ local as 60664; neighbor 153.92.124.4 as 60664; source address 185.27.180.133; enable route refresh yes; multihop; allow local as 60664; ipv4 { import all; export all; next hop self; }; } router E and F (VALID): BIRD SHOW ROUTE birdc show route 223.230.128.0/22 all BIRD 2.0.5 ready. Table master4: 223.230.128.0/22 unicast [routerE_to_routerA 02:42:58.878 from 153.92.124.4] * (100/?) [AS45609?] via 192.168.0.1 on external Type: BGP univ BGP.origin: Incomplete BGP.as_path: 15943 9498 45609 BGP.next_hop: 153.92.124.4 BGP.local_pref: 100 KERNEL route -n | grep 204.34.123.0 204.34.123.0 192.168.0.1 255.255.255.0 UG 32 0 0 external CONFIG protocol bgp routerE_to_routerA{ local as 60664; neighbor 153.92.124.4 as 60664; source address 192.168.0.2; multihop; allow local as 60664; ipv4 { import all; export all; next hop self; }; } router A BIRD SHOW ROUTE birdc show route 223.230.128.0/22 all BIRD 2.0.5 ready. Table master4: 223.230.128.0/22 unicast [routerA_to_external 23:01:24.661] * (100) [AS45609?] via 84.44.0.210 on xge1 Type: BGP univ BGP.origin: Incomplete BGP.as_path: 15943 9498 45609 BGP.next_hop: 84.44.0.210 BGP.local_pref: 100 KERNEL route -n | grep 204.34.123.0 204.34.123.0 84.44.0.210 255.255.255.0 UG 32 0 0 xge1 CONFIG E (valid) protocol bgp routerA_to_routerE{ local as 60664; neighbor 153.92.124.2 as 60664; source address 153.92.124.4; direct; allow local as 60664; ipv4 { import all; export all; next hop self; }; } CONFIG G (problem) protocol bgp routerA_to_routerG{ local as 60664; neighbor 185.27.180.133 as 60664; source address 153.92.124.4; multihop; allow local as 60664; ipv4 { import all; export all; gateway recursive; next hop self; }; } I am using bird 2.0.5 and ubuntu 18.04 with 4.15.0-54-generic and already played around with and without "next hop self" etc. but without luck. There seems to be a problem with my configuration or with the next hop calculation, right? Or did i miss something else? Thank you in advance Martin Bosner

3 3

Segmentation fault on 2.0.5
by Radu Anghel 14 Aug '19

14 Aug '19

Hello, I recently upgraded BIRD from 2.0.4 to 2.0.5 and with the same (pretty large) .conf I got Segmentation fault. Until today I didn't have time to debug it, but here it goes: With this simple .conf I get seg fault on 2.0.5 while 2.0.4 works as expected. (if I define myvar = true it doesn't crash on 2.0.5) log syslog all; define myvar = false; function something () { if myvar then { return false; } return true; } protocol device DEVICE { } Could this be because of the new filter code or something else? Radu

3 3

BGP table size
by Emerson Barea 13 Aug '19

13 Aug '19

Hi. Anyone knows if Bird documentation has any information about BGP table size vs. number of routes? Thanks. Emerson

7 13

Some patches for FreeBSD
by Vincent Bernat 12 Aug '19

12 Aug '19

Hey! Here are a few patches for FreeBSD. They are targeted to the "legacy" branch, but the two last ones can be applied to the master branch as well.

3 5

[PATCH 2/3] BSD: don't complain about interfaces without IP addresses
by Vincent Bernat 12 Aug '19

12 Aug '19

Without this patch, BIRD complains about interfaces without an IP address: 2019-08-12 07:41:26 <ERR> KIF: Invalid interface address 0.0.0.0 for vtnet2 --- sysdep/bsd/krt-sock.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sysdep/bsd/krt-sock.c b/sysdep/bsd/krt-sock.c index f0cebd11c5b7..f92cf1a68dc6 100644 --- a/sysdep/bsd/krt-sock.c +++ b/sysdep/bsd/krt-sock.c @@ -651,6 +651,8 @@ krt_read_addr(struct ks_msg *msg, int scan) imask = ipa_from_sa(&mask); ibrd = ipa_from_sa(&brd); + if (ipa_zero(iaddr)) + return; if ((masklen = ipa_masklen(imask)) < 0) { -- 2.23.0.rc1

1 0

Anyone used 'missing lladdr' option?
by Ondrej Zajicek 08 Aug '19

08 Aug '19

Hi I just noticed that since transition to 2.0, BGP option 'missing lladdr' is not implemented. I wonder if anyone used this option or whether we should just remove it. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago(a)crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."

3 3

sets in bgpmasks ?
by Clemens Schrimpe 06 Aug '19

06 Aug '19

Hello all - I wonder: Is there a "nice" syntax to have sets (lists of ASs) inside of bgpmasks? I.e., [= 123 [234, 345] * =] does not work (syntax error). Any other ideas? Thanks, Clemens

4 6

BIRD 2.0.5 build failures on RHEL/CentOS 6 and 7
by Robert Scheck 06 Aug '19

06 Aug '19

Hello all, I'm seeing the following build failures with BIRD 2.0.5 on RHEL/CentOS 6, while BIRD 2.0.4 worked fine (just did a BIRD version bump, not more): --- snipp --- BUILDSTDERR: obj/conf/cf-parse.y: In function 'cf_parse': BUILDSTDERR: obj/conf/cf-parse.y:1918: error: unknown field 'asn' specified in initializer BUILDSTDERR: obj/conf/cf-parse.y:1918: warning: missing braces around initializer BUILDSTDERR: obj/conf/cf-parse.y:1918: warning: (near initialization for '(anonymous).val.pmi.<anonymous>') BUILDSTDERR: obj/conf/cf-parse.y:1919: error: unknown field 'from' specified in initializer BUILDSTDERR: obj/conf/cf-parse.y:1919: warning: missing braces around initializer BUILDSTDERR: obj/conf/cf-parse.y:1919: warning: (near initialization for '(anonymous).val.pmi.<anonymous>') BUILDSTDERR: obj/conf/cf-parse.y:1919: error: unknown field 'to' specified in initializer BUILDSTDERR: obj/conf/cf-parse.y:2172: error: unknown field 'sym' specified in initializer BUILDSTDERR: obj/conf/cf-parse.y:2172: warning: missing braces around initializer BUILDSTDERR: obj/conf/cf-parse.y:2172: warning: (near initialization for '(anonymous).<anonymous>') BUILDSTDERR: obj/conf/cf-parse.y:2174: error: unknown field 'sa' specified in initializer BUILDSTDERR: obj/conf/cf-parse.y:2174: warning: missing braces around initializer BUILDSTDERR: obj/conf/cf-parse.y:2174: warning: (near initialization for '(anonymous).<anonymous>') BUILDSTDERR: obj/conf/cf-parse.y:2174: error: incompatible types when initializing type 'struct symbol *' using type 'struct f_static_attr' BUILDSTDERR: obj/conf/cf-parse.y:2175: error: unknown field 'da' specified in initializer BUILDSTDERR: obj/conf/cf-parse.y:2175: warning: missing braces around initializer BUILDSTDERR: obj/conf/cf-parse.y:2175: warning: (near initialization for '(anonymous).<anonymous>') BUILDSTDERR: obj/conf/cf-parse.y:2175: error: incompatible types when initializing type 'struct symbol *' using type 'struct f_dynamic_attr' BUILDSTDERR: obj/conf/cf-parse.y:2403: warning: pointer targets in assignment differ in signedness BUILDSTDERR: obj/conf/cf-parse.y:2404: warning: pointer targets in assignment differ in signedness --- snapp --- https://kojipkgs.fedoraproject.org/work/tasks/4846/36814846/build.log is the full log (will be auto-cleaned up in a couple of days). And even building on RHEL/CentOS 7 fails now (also just a BIRD version bump): --- snipp --- BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans0.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans1.ltrans.o: relocation R_X86_64_32 against hidden symbol `sk_class.61292' can not be used when making a shared object BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans2.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans3.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans4.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans5.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans6.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans7.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans8.ltrans.o: relocation R_X86_64_32S against hidden symbol `opaque_lsa_types_inv.40457' can not be used when making a shared object BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans9.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans10.ltrans.o: relocation R_X86_64_32S against hidden symbol `proto_bgp' can not be used when making a shared object BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans11.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans12.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans13.ltrans.o: relocation R_X86_64_32S against hidden symbol `proto_bgp' can not be used when making a shared object BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans14.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans15.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans16.ltrans.o: relocation R_X86_64_32S against hidden symbol `bfd_wait_list.24893' can not be used when making a shared object BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans17.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans18.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans19.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans20.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans21.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans22.ltrans.o: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans23.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans24.ltrans.o: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans25.ltrans.o: relocation R_X86_64_32 against hidden symbol `b.8691.10727' can not be used when making a shared object BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans26.ltrans.o: relocation R_X86_64_32 against hidden symbol `filter_state.9587' can not be used when making a shared object BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans27.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans28.ltrans.o: relocation R_X86_64_32S against hidden symbol `yy_accept.7797' can not be used when making a shared object BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans29.ltrans.o: relocation R_X86_64_32S against hidden symbol `yypact.4429' can not be used when making a shared object BUILDSTDERR: /usr/bin/ld: /tmp/ccZUW9JI.ltrans30.ltrans.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC BUILDSTDERR: /usr/bin/ld: final link failed: Nonrepresentable section on output --- snapp --- https://kojipkgs.fedoraproject.org//work/tasks/5313/36815313/build.log is the full log (will be auto-cleaned up in a couple of days). While I indeed can pass -fPIC myself (leading to a successful build), I still wonder why these changes happened and whether you maybe missed some autoconf/automake-foo to cover it "automagically". Regards, Robert

4 7

Option --runstatedir in BIRD 2.0.4 broken?
by Robert Scheck 06 Aug '19

06 Aug '19

Hello folks, when trying to use --runstatedir in BIRD 2.0.4, it looks like this here: + ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --runstatedir=/run/bird BUILDSTDERR: configure: error: unrecognized option: `--runstatedir=/run/bird' https://kojipkgs.fedoraproject.org//work/tasks/7262/33807262/build.log is the full buildsystem log. So is --runstatedir in BIRD 2.0.4 broken? When looking to configure, it feels very much like a autoconf generation issue. Because in difference to that BIRD 2.0.3 doesn't complain, buildsystem log: https://kojipkgs.fedoraproject.org//work/tasks/7292/33807292/build.log Regards, Robert

3 4