May 2019 - Bird-users - Mailing Lists

Help with SNMP for BIRD
by Glenn Peace 28 May '19

28 May '19

Good afternoon everyone, I hope this message finds you well. We would like to monitor the BGP session stablished by our BIRD Route server with monitoring tools like Nagios or LibreNMS. I’ve found a couple email threads indicating this was not directly available a couple years ago. On the other hand, some web sites suggest tools for this purpose, but I’m u sure if they are reliable. Is this now available with BIRD? Or, can you suggest a tool for this? Best, N I C . C R Glenn Peace Sr. Network Engineer gtpeace(a)nic.cr

4 5

Received route with strange next-hop
by Adrichem, N.L.M. (Niels) van 28 May '19

28 May '19

Hello, I'm trying to redistribute routes from another routing daemon through synchronization of the kernel table using the kernel protocol in BIRD 2.0.4. However, I run into some problems that not all routes are imported by the BIRD router. The kernel routing table contains the following routing table: # ip route 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.1 10.0.1.3 via 10.0.1.4 dev eth1 proto zebra metric 2 10.0.1.4 dev eth1 proto zebra scope link metric 1 10.0.4.0/24 via 10.0.0.2 dev eth0 proto bird metric 32 The interface eth1 has the address 10.0.1.1/32 in an ad-hoc routing domain, through OSPF-MDR (which is an extension of Quagga) it finds the direct neighbor 10.0.1.4 which is added as "10.0.1.4 dev eth1 proto zebra scope link metric 1". The neighbor 10.0.1.4 advertises that it can forward to 10.0.1.3 which is added as "10.0.1.3 via 10.0.1.4 dev eth1 proto zebra metric 2". The routing of OSPF-MDR works, in the sense that 10.0.1.1 can reach 10.0.1.3 and 10.0.1.4. However, when we try to import these routes from the protocol kernel into the Bird routing table, only the directly connected route to 10.0.1.4 shows while the route to 10.0.1.3 are not imported: # birdc show route BIRD 2.0.4 ready. Table master4: 10.0.1.4/32 unicast [kernel1 10:27:29.329] (10) dev eth1 10.0.4.0/24 unicast [babel1 10:27:23.461 from fe80::200:ff:feaa:4] (130/96) [00:00:00:00:0a:00:00:02] via 10.0.0.2 on eth0 10.0.0.0/24 unicast [direct1 10:27:21.870] * (240) dev eth0 unicast [babel1 10:27:23.461 from fe80::200:ff:feaa:4] (130/96) [00:00:00:00:0a:00:00:02] via 10.0.0.2 on eth0 Additionally, the bird.log file throws the following error: 2019-05-15 10:27:21.869 <INFO> Started 2019-05-15 10:27:21.902 <WARN> Missing broadcast address for interface vxlan0 2019-05-15 10:27:29.329 <ERR> KRT: Received route 10.0.1.3/32 with strange next-hop 10.0.1.4 It may be that kernel protocol rejects the route because the next-hop is not in the interface its regular netmask (which is set to /32), though I am not familiar enough with the source code to determine the exact cause except that the error gets thrown from sysdep/linux/netlink.c line 1643. However, I think the line should be accepted since there is another routing rule confirming that the next-hop is directly attached to device eth1. Given the explicit error I don't think this is a configuration error (though I am open to learn more), so I hope BIRD can be patched to solve this. I have attached the bird.conf file, as well as an image of the example topology. Above snippets and config file are taken from node n1 which is running both the OSPF-MDR router based on Quagga and BIRD Router. Any help would be much appreciated. Thanks in advance, Niels van Adrichem [cid:image001.png@01D50B0D.4706B540] This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.

2 2

Hardware Server requirements for building up BIRD
by Isaac HO 28 May '19

28 May '19

Dear All, Would you mind suggesting the hardware configuration to us? Please find our BGP sessions status for your reference: IPv4 Session 600 (around) IPv6 Session 400 (around) Thanks, Isaac

3 3

Simple two bird BGPs two Uplinks one Peering Provider config
by Yves Illi 26 May '19

26 May '19

Hi there, I am really new to the complete topic of BGP. So please have a bit mercy with me if I ask something very stupid. But I am trying to build that for the first time ever and I am feeling like a donkey in front of a big mountain. Last but not least it is currently running, but I guess its more luck than something else. Like I said I am completely new to the topic of BGP. What I don't get is how I configure them together so they work (as a HA-Cluster) and currently I can only route a.b.c.249/29 instead of a.b.c.0/22. Here is what I am trying to build (https://imgur.com/a/NtWE6MY) And here are my two configs: /* * My example bgp01 configuration */ log syslog all; log "/var/log/bird.log" all; # d.e.f.124/29 is my IP in the transfer network /29 to my peering uplink1 # d.e.f.125/29 is my 2nd bird bgp in the transfer network /29 to my peering uplink1 router id d.e.f.124; define myasn = XXXX; define myaddr = d.e.f.124; protocol device { scan time 10; # Scan interfaces every 10 seconds } ipv4 table master4; protocol direct { ipv4; # Tells bird to only do ipv4 interface "enp3s0f4"; # Restrict network interfaces BIRD works with } protocol kernel { ipv4{ table master4; import all; export all; }; persist; } #a.b.c.0 is my own /22 ip range protocol static static_bgp { ipv4; route a.b.c.0/22 via d.e.f.124; } protocol bgp link1 { local d.e.f.124 as XXXX; neighbor d.e.f.121 as YYYY; #d.e.f.121 is the first router of my peering uplink 1 ipv4 { import all;export where proto = "static_bgp"; }; } protocol bgp link2 { local d.e.f.124 as XXXX; neighbor d.e.f.122 as YYYY; #d.e.f.122 is the second router of my peering uplink 1 ipv4 { import all;export where proto = "static_bgp"; }; } /* * My example bgp02 configuration */ log syslog all; log "/var/log/bird.log" all; # d.e.f.124/29 is my IP in the transfer network /29 to my peering provider1 # d.e.f.125/29 is my 2nd bird bgp in the transfer network /29 to my peering provider1 router id d.e.f.125; define myasn = XXXX; define myaddr = d.e.f.125; protocol device { scan time 10; # Scan interfaces every 10 seconds } ipv4 table master4; protocol direct { ipv4; # Tells bird to only do ipv4 interface "enp3s0f4"; # Restrict network interfaces BIRD works with } protocol kernel { ipv4{ table master4; import all; export all; }; persist; } #a.b.c.0 is my own /22 ip range protocol static static_bgp { ipv4; route a.b.c.0/22 via d.e.f.125; } protocol bgp link1 { local d.e.f.125 as XXXX; neighbor d.e.f.121 as YYYY; #d.e.f.121 is the first router of my peering provider1 ipv4 { import all;export where proto = "static_bgp"; }; } protocol bgp link2 { local d.e.f.125 as XXXX; neighbor d.e.f.122 as YYYY; #d.e.f.122 is the second router of my peering provider1 ipv4 { import all;export where proto = "static_bgp"; }; } Thanks a lot for your help and inputs Best Regards, Yves

4 5

bird external script hook?
by Michael Schwartzkopff 23 May '19

23 May '19

Hi, some time ago there was in interesting discussion to add hooks to call external scripts to bird. See: https://bird.network.cz/pipermail/bird-users/2014-July/009167.html As far as ask my google, these hooks are not yet implemented in bird. Am I correct? Any idea how to get an external script run after a route change? Mit freundlichen Grüßen, -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

2 1

bgp add paths to select only equal routes
by Alexander Zubkov 16 May '19

16 May '19

Hello, If "add paths" config option is enabled for a bgp protocol than it sends every route matching the filter on export. But I would like to have an option to send only the best route with routes similar to it (equal localpref, aspath length, ...). Like it is done in the kernel protocol and its "merge paths" option. So for example if I had 2 routes for the same prefix with different bgp_local_pref or bgp_path length, than only the route with better attributes would be announced to the peer. Currently both routes would be announced.

2 2

show route for ... filtered (not working)
by Terra Nova 13 May '19

13 May '19

Greetings, Ubuntu-16.04.6 LTS bird-1.6.6 (built from source) Our upstream BGP configuration is using: import keep filtered on I was checking the master table for a (filtered) destination IPv6 address (and network) doing the following. bird> show route for 2620:0:6b0:ff00::20 Network not in table bird> show route for 2620:0:6b0:ff00::20 all Network not in table bird> show route for 2620:0:6b0:ff00::20 filtered Network not in table bird> show route where bgp_path ~ [= * 23028 =] bird> show route where bgp_path ~ [= * 23028 =] filtered 2604:8800::/32 via 2001:590::xxxx:xxxx on edge.411 [gtt6 01:53:36] * (100 / 95) [AS 820048060 174 23028i] 2620:0:6b0::/48 via 2001:590::xxxx:xxxx on edge.411 [gtt6 01:53:36] * (100 / 95) [AS 820048060 174 23028i] bird> show route filtered for 2604:8800::/32 Network not in table bird> show route for 2604:8800::/32 filtered Network not in table bird> show route for 2620:0:6b0::/48 filtered Network not in table bird> show route table master for 2620:0:6b0:ff00::20 filtered Network not in table Why will the 'show route' only show this filtered route using 'bgp_path' and not directly using 'for'? This route is filtered in the 'master' table and there are no Pipes being used. Am I misusing the 'filtered' option? Thank you for looking. -- Terra

3 4

'prefer older' does not work?
by Alexander Shikov 13 May '19

13 May '19

Hello! All of our BGP peers have 'prefer older' option enabled. But I noticed that best route is not the oldest one: bird> show route for 91.226.190.1 all 91.226.190.0/24 via 193.25.181.44 on bge0 [ITSTARCOM 2019-05-10 11:05:56] * (100) [AS50981i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 48422 50981 BGP.next_hop: 193.25.181.44 BGP.local_pref: 100 BGP.community: (65005,10804) (31210,31210) BGP.ext_community: (rt, 31210, 31210) via 193.25.180.141 on bge0 [SATELLITE 2019-05-09 15:16:08] (100) [AS50981i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 44416 50981 BGP.next_hop: 193.25.180.141 BGP.local_pref: 100 BGP.community: (44416,2) (65005,10804) (31210,31210) BGP.ext_community: (rt, 31210, 31210) What am I missing? Thanks! -- Alexander Shikov Technical Staff, Digital Telecom IX Tel.: +380 44 201 14 07 Mob.: +380 50 410 30 57 http://dtel-ix.net/

3 3

Debian packages for BIRD2
by Kees Meijs 13 May '19

13 May '19

Hi list, Yesterday I attended T-DOSE (http://t-dose.org/) and spoke to some other BIRD users, mostly on Debian. As a collective, we were a little surprised that https://bird.network.cz/?download&tdir=debian/pool/main/b/bird/ only shows BIRD 1.6 packages and not 2.0. Compiling 2.0 (at least for Stretch; didn't test Buster yet) works quite well, for example when using the tree as of https://salsa.debian.org/debian/bird2/ Maybe there's another place to look (and we didn't look in the right place) or maybe there's simply no one compiling the packages for the public. If applicable, I would like to help out albeit by hosting a package repository or compiling (or both). Cheers, Kees -- https://nefos.nl/contact Nefos IT bv Ambachtsweg 25 (industrienummer 4217) 5627 BZ Eindhoven Nederland KvK 66494931 /Aanwezig op maandag, dinsdag, woensdag en vrijdag/

8 8

static default route not always pushed to kernel (2.0.4)
by Kenth Eriksson 08 May '19

08 May '19

Hi! There are cases where bird does not push a static default route to the kernel. One way to see this is as follows; A default route from the kernel bird> show route for 0.0.0.0 Table master4: 0.0.0.0/0 unicast [kernel1 13:46:07.958] (215) via 10.210.137.1 on eth1 Add two static default routes bird> show static 0.0.0.0/0 via 10.210.137.1 0.0.0.0/0 via 192.168.120.1 (dormant) bird> The static default route has higher preference, hece I expected it to be pushed to the kernel. But it is not... bird> show route for 0.0.0.0 Table master4: 0.0.0.0/0 unicast [kernel1 13:46:07.958] (215) via 10.210.137.1 on eth1 bird> Next remove both static routes, configure, add one of them back again and both are shown. bird> show route for 0.0.0.0 Table master4: 0.0.0.0/0 unicast [static1 14:13:16.762] * (255) via 10.210.137.1 on eth1 unicast [kernel1 13:46:07.958] (215) via 10.210.137.1 on eth1 bird> Thanks, Kenth

3 11