- Bird-users - Mailing Lists

comparing open source BGP stacks performance
by Justin Pietsch 26 Aug '21

26 Aug '21

Hi all, because I couldn't find many results of performance tests of open source routing stacks, I did some tests and wrote up https://elegantnetwork.github.io/posts/comparing-open-source-bgp-stacks/. It compares BIRD, FRRouting and GoBGP. Justin

7 7

IPv6 BGP & kernel 4.19
by Robert Sander 25 Aug '21

25 Aug '21

Hi, our routers run on Debian stretch with bird 1.6.4 from bird.network.cz/debian. Yesterday I tried kernel 4.19 from backports.debian.org and ran into a weird issue with IPv6 BGP sessions: All Peerings reported "Error: Hold timer expired" ca. every 40 minutes. IPv6 forwarding was flapping all the time. After rebooting into kernel 4.9 everything worked again. IPv4 BGP was not affected and also OSPF (v4 and v6). I could disable all IPv6 BGP peerings on this router and then it forwarded to another router learned via OSPF for IPv6 without issues. Has anyone seen such a behaviour? Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 93818 B Geschäftsführer: Peer Heinlein - Sitz: Berlin

13 39

Routes imported from BGP doesn't have proper gateways
by Ooth Gray 23 Aug '21

23 Aug '21

Hi I'm having troubles in BIRD configuration, and I'm pretty sure it's just a trivial wrong configure issue but I really tried my best >_< Let me give you some background. 1. There are 2 hosts connected by wire (so that they are L2 reachable), one with IPv4 10.22.12.88, and another is 10.22.12.44. Here's one the arp record from "ip neigh sh": > 10.22.12.88 dev bond0 lladdr f8:6e:ee:8b:cf:90 REACHABLE > 2. Both 2 hosts have some KVM virtual machines, with corresponding routes from host to vm, here's one of the routes from "ip r": > 10.233.25.178 dev yap35caa1e88854 scope link src 10.22.12.44 The 10.233.25.178 is the address of a VM, and the dev yap35caa1e88854 is a tap device connecting eth0 inside the VM. What I want to do is to build routes between these 2 hosts, in order to let VMs on host A be able to connect VMs on host B. Hope I make myself clear. So I'm using BIRD 2.0.3 on Ubuntu 16.04, with the config file as follows: log syslog all; > router id 10.22.12.44; > > protocol device { > debug { states }; > scan time 2;} > > protocol kernel { > learn; > persist; > scan time 10; > ipv4 { > import all; > export all; > };} > > protocol bgp { > debug { states }; > local as 65000; > neighbor 10.22.12.88 as 65000; > source address 10.22.12.44; > multihop; > ipv4 { > export filter { > if ( net ~ 10.233.0.0/16 ) then { > accept; > } > reject; > }; > import all; > next hop self on; > gateway recursive; > add paths on; > };} > > But this doesn't work well, the peer BIRD show the info as follows: bird> show route protocol bgp1 > Table master4:10.233.25.178/32 unicast [bgp1 18:47:32.910 from 10.22.12.44] * (100/?) [i] > via 10.22.12.1 on enp2s0f0 onlink > bird> show route export kernel1 > Table master4:10.233.25.178/32 unicast [bgp1 18:47:32.910 from 10.22.12.44] * (100/?) [i] > via 10.22.12.1 on enp2s0f0 onlink > > The problem happened on the gateway, I was hoping the routes should have "via 10.22.12.44" instead of "via 10.22.12.1"; 10.22.12.1 came from the host default gateway: > default via 10.22.12.1 dev bond0 onlink But I have no idea how to prevent BIRD from using it. The other information may be helpful is included below: bird> show protocols all bgp1 > Name Proto Table State Since Info > bgp1 BGP --- up 18:28:46.888 Established > BGP state: Established > Neighbor address: 10.22.12.88 > Neighbor AS: 65000 > Neighbor ID: 10.22.12.88 > Local capabilities > Multiprotocol > AF announced: ipv4 > Route refresh > Graceful restart > 4-octet AS numbers > ADD-PATH RX: ipv4 TX: ipv4 > Enhanced refresh > Long-lived graceful restart > Neighbor capabilities > Multiprotocol > AF announced: ipv4 > Route refresh > Graceful restart > 4-octet AS numbers > Enhanced refresh > Long-lived graceful restart Session: internal multihop AS4 > Source address: 10.22.12.44 > Hold timer: 117.086/240 > Keepalive timer: 52.520/80 > Channel ipv4 State: UP Table: master4 Preference: 100 > Input filter: ACCEPT > Output filter: (unnamed) Routes: 2 imported, 20 exported > Route change stats: received rejected filtered ignored accepted > Import updates: 2 0 0 0 2 > Import withdraws: 0 0 --- 0 0 > Export updates: 49 6 23 --- 20 > Export withdraws: 0 --- --- --- 4 > BGP Next hop: 10.22.12.44 > IGP IPv4 table: master4 > > bird> show route export bgp1 > Table master4:10.233.25.178/32 unicast [kernel1 18:04:09.483] (10) > dev yap35caa1e88854 > > Please enlighten me with some advice, and I'll appreciate that very much. Thank you!

2 2

bird-2.0.8 in Debian experimental
by Jakub Ružička 23 Aug '21

23 Aug '21

Hello Community, I've finally managed to upload bird2-2.0.8 into Debian experimental \o/ If you're waiting for official Debian BIRD packages, please consider testing the experimental version and letting me know whether it worked for you as expected. tl;dr HOWTO test on Debian unstable (sid): echo "deb http://deb.debian.org/debian experimental main" >> /etc/apt/sources.list apt update apt -t experimental install bird2 # TEST ALL THE THINGS As I'm new to BIRD Debian packaging, I've also CCd the friendly Debian Developer Marco who offered help - if he or anyone else with Debian knowledge could validate my BIRD package changes, that would be great: https://salsa.debian.org/debian/bird2/-/commits/experimental I've also enabled Salsa CI which is currently red only due to an unrelated lintian/debhelper issue #992469. If all is good, I'd like to submit 2.0.8 for unstable/testing and perhaps bullseye-backports eventually. Cheers, Jakub Ružička CZ.NIC packager 📦

1 0

prefix can't be export by BGP
by 智慧雨泽 17 Aug '21

17 Aug '21

Hi, bird user It seems that the image attachment cannot be seen by others, so I resend it ( I want to export 2602:feda:ab4::/48. I wrote 「if bgp_export() then accept」 in the BGP template, but it was not exported to BGP correctly. But bgp_export() outputs 2602:feda:ab4::/48. I can't find the BGP in the bird document under what circumstances will not export prefix, please tell me, thanks! bird> show route export Hurricane_Electric_LLC Table master6: 2a10:cc44:100::/44 unicast [UNM_Exch_RS2 2021-08-13 from 2602:ffb1:200:0:192:34:27:253] * (100) [AS38281i] via 2602:ffb1:200:0:192:34:27:6 on ens19 2a10:cc44:109::/48 unicast [LL_IX 15:22:24.526] * (100) [AS38281i] via 2602:feda:ab2:5247:5247:5247:5247:5247 on ll_ix 2001:df6:9f80::/48 unicast [EVIX_RS1 2021-08-13 from 2602:fed2:fff:ffff::1] * (100) [AS38281i] via 2602:fed2:fff:ffff::107 on ens20 2602:feda:ab2::/48 unicast [LL_IX 2021-08-15] * (100) [AS141011i] via 2602:feda:ab2:5247:5247:5247:5247:5247 on ll_ix bird> bird> show route where bgp_export() all Table master6: 2602:feda:ab2::/48 unicast [LL_IX 2021-08-15] * (100) [AS141011i] via 2602:feda:ab2:5247:5247:5247:5247:5247 on ll_ix Type: BGP univ BGP.origin: IGP BGP.as_path: 141011 BGP.next_hop: 2602:feda:ab2:5247:5247:5247:5247:5247 fe80::200:5efe:5bd:ff6b BGP.local_pref: 100 2602:feda:ab4::/48 unreachable [BGP_Prefix 2021-08-13] (200) Type: static univ bird> template bgp tpl_bgp { graceful restart on; local as LOCAL_ASN; ipv6 { next hop self; import filter peer_in_v6; #export where bgp_export(); export filter{ #if my_opt_prefix() then bgp_path.prepend(LOCAL_ASN); if bgp_export() then accept; if bgp_export_downstream() then accept; else reject; }; }; }

2 2

Couldn't announce the prefix
by 智慧雨泽 16 Aug '21

16 Aug '21

Hi, bird user I want to export 2602:feda:ab4::/48. I wrote 「if bgp_export() then accept」 in the BGP template, but it was not exported to BGP correctly. But bgp_export() outputs 2602:feda:ab4::/48, Please see the picture below. [image: image.png] [image: image.png] [image: image.png] Also what kind of case BGP will not export the prefix? I couldn't find it in the documentation.

1 0

Debian 11 (Bullseye) Repository
by Peter Potvin 16 Aug '21

16 Aug '21

Good evening, With the official release of Debian 11 (Bullseye) Stable occurring less than 48 hours ago, it would be nice to know of the timeline for which BIRD 2.0.8 will be added to the official Debian repository or a reputable third-party repository. Regards, Peter

5 5

BIRD Debian Repo signing keys need updating
by Laura Smith 16 Aug '21

16 Aug '21

See https://github.com/oerdnj/deb.sury.org/issues/1325 which highlights wrong keys being published. TL;DR - @oerdnj left cz.nic three years ago but you are still publishing wrong keys on the repo ?

2 2

[PATCH 1/2] Add mips Debian 8 container
by Skyler Mäntysaari 15 Aug '21

15 Aug '21

Hi! I hope that this will work and help with the mips package building. I originially had forgotten to do the pkg gitlab steps too. Please let me know if I can help with that in any other way and disregard the previous patch. This is basically the same one, with both commits. --- .gitlab-ci.yml | 10 ++++++++++ misc/docker/debian-9-mips/Dockerfile | 26 ++++++++++++++++++++++++++ 2 files changed, 36 insertions(+) create mode 100644 misc/docker/debian-9-mips/Dockerfile diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 3642b671..f6a5bb39 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -17,6 +17,7 @@ stages: allow_failure: true script: - $DOCKER_CMD login -u gitlab-ci-token -p $CI_BUILD_TOKEN registry.labs.nic.cz + - $DOCKER_CMD --rm --privileged aptman/qus -s -- -p mips # Make sure we refresh the base image if it updates (eg. security updates, etc) # If we do just the build, cache is always reused and the freshness of the # base image is never checked. However, pull always asks and updates the @@ -52,6 +53,11 @@ docker_debian-9-i386: IMG_NAME: "debian-9-i386" <<: *docker_build +docker_debian-9-mips: + variables: + IMG_NAME: "debian-9-mips" + <<: *docker_build + docker_debian-10-amd64: variables: IMG_NAME: "debian-10-amd64" @@ -248,6 +254,10 @@ build-debian-9-i386: <<: *build-linux image: registry.labs.nic.cz/labs/bird:debian-9-i386 +build-debian-9-mips: + <<: *build-linux + image: registry.labs.nic.cz/labs/bird:debian-9-mips + build-debian-10-amd64: <<: *build-linux image: registry.labs.nic.cz/labs/bird:debian-10-amd64 diff --git a/misc/docker/debian-9-mips/Dockerfile b/misc/docker/debian-9-mips/Dockerfile new file mode 100644 index 00000000..1600011b --- /dev/null +++ b/misc/docker/debian-9-mips/Dockerfile @@ -0,0 +1,26 @@ +FROM multiarch/debian-debootstrap:mips-stretch-slim +ENV DEBIAN_FRONTEND noninteractive +RUN sed -i 's/deb.debian.org/ftp.cz.debian.org/' /etc/apt/sources.list +RUN apt-get -y update +RUN apt-get -y upgrade +RUN apt-get -y --no-install-recommends install \ + build-essential \ + flex \ + bison \ + autoconf \ + ncurses-dev \ + libreadline-dev \ + libssh-gcrypt-dev \ + linuxdoc-tools-latex \ + texlive-latex-extra \ + opensp \ + docbook-xsl \ + xsltproc +RUN apt-get -y --no-install-recommends install \ + git \ + dpkg-dev \ + debhelper \ + quilt \ + python3 \ + python3-pip \ + python3-setuptools -- 2.26.3

2 6

bird 2.0.8 ignores local routes during import?
by Tim Meusel 12 Aug '21

12 Aug '21

Hi, I'm running bird 2.0.8 on Arch Linux: I would like to import local device routes and export them via BGP. My assumption is that the direct protocol would be required here? My config looks like this: router id 192.168.178.35; debug protocols all; log syslog { debug, trace, info, remote, warning, error, auth, fatal, bug }; timeformat protocol iso long; protocol device { scan time 10; interface "uplink" { preferred 192.168.178.35; }; } protocol kernel kernelv4 { learn; persist; scan time 20; ipv4 { import all; export filter { if source = RTS_STATIC then reject; krt_prefsrc = OWNIP; accept; }; }; } protocol direct { ipv4; ipv6; interface "uplink"; } The box has a few local routes: # ip -4 r s default via 192.168.178.1 dev enp3s0 proto dhcp src 192.168.178.35 metric 1024 169.254.0.7 dev as3668-1 proto kernel scope link src 169.254.0.8 169.254.0.9 dev as3668-2 proto kernel scope link src 169.254.0.10 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.178.0/24 dev enp3s0 proto kernel scope link src 192.168.178.35 metric 1024 192.168.178.1 dev enp3s0 proto dhcp scope link src 192.168.178.35 metric 1024 But it looks like the direct protocol doesn't import any routes and via the kernel I don't get theh route for 192.168.178.0/24? root@server ~ # birdc show route protocol device1 BIRD 2.0.8 ready. No valid tables root@server ~ # birdc show route protocol kernelv4 BIRD 2.0.8 ready. Table master4: 0.0.0.0/0 unicast [kernelv4 2021-08-08] * (10) via 192.168.178.1 on enp3s0 192.168.178.1/32 unicast [kernelv4 2021-08-08] * (10) dev enp3s0 root@server ~ # any clues why I don't see see "192.168.178.0/24 dev enp3s0" route in bird? Cheers, Tim

1 1