November 2016 - Bird-users

Version 1.6.2
by Ondrej Filip 31 Aug '17

31 Aug '17

Dear users, a new version of the 1.6.x branch is out: Version 1.6.2 (2016-09-29) o Fixes serious bug introduced in the previous version Upgrade from 1.6.1 is highly recommended. Enjoy it! Ondrej

4 6

BGP Monitoring Protocol (BMP) support in Bird?
by Baptiste Jonglez 11 Jul '17

11 Jul '17

Hi, I am wondering if somebody is working on BGP Monitoring Protocol (BMP) support in Bird? Note that I'm just asking, I'm not requesting our beloved Bird developers to add this feature with a deadline set to yesterday :) I might try to implement it if nobody else already did. Basically, this is just a way to export BGP data over a TCP connection: http://tools.ietf.org/html/rfc7854 This looks like a useful alternative to dumping to mrtdump files, there are already several free software clients: https://code.google.com/archive/p/bmpreceiver/ http://www.openbmp.org/#!index.md Baptiste

3 3

Route attributes overwritten during reconfiguration
by João Taveira Araújo 17 Feb '17

17 Feb '17

Hi, I've run into a bug which manifests itself during reconfiguration. Unfortunately, the bird config in question is extremely large and I can't easily cut it down to something replicable. I'm running into this particular issue in bird6, but have no reason to believe IPv4 would fair any better. All results are using bird 1.6.2. My setup is as follows: - a static protocol, in which the import stanza adds extended communities: route 2001:db8::/48 via "lo" { bgp_ext_community.add((ro, 2, 0)); bgp_ext_community.add((ro, 3, 0)); ... } - based on these communities, the static route makes its way through a pipe from the master table, to an external table Typically all is fine - we export the route to our transits. Since we have multiple egress devices, a "show route" will show our local, static route, as well as the same route learnt through our providers: sudo birdc6 show route for 2001:db8::/48 BIRD 1.6.2 ready. 2001:db8::/48 dev lo [static_protocol 04:42:26] * (200) via xxx on et1 [transit_1 03:44:07] (100) via xxx on et2 [transit_2 03:44:07] (100) We actually have three transits, but one of our transits does not export any routes we happen to be exporting to them. Such a case happens on reconfiguring BIRD. During a reconfiguration, the static protocol gets reloaded: <TRACE> static_protocol > 2001:db8::/48 added [best] dev lo in this brief moment, a window of opportunity arises for our thus far silent transit to make an unwanted appearance: sudo birdc6 show route for 2001:db8::/48 BIRD 1.6.2 ready. 2001:db8::/48 dev lo [static_protocol 05:44:07] * (200) via xxx on et3 [transit_3 05:44:07] (100) via xxx on et1 [transit_1 03:44:07] (100) via xxx on et2 [transit_2 03:44:07] (100) This, it turns out, is tragic, because somehow the extended communities we apply to the route learnt from transit_3 clobber the ones we apply in static_protocol. I'm pretty sure something screws up the rta associated to the static route, but I'm also confused as to why the static protocol seems to get reloaded at all given there is no configuration change in the first place. We definitely want to allow local as: since the routes are potentially anycast, it is useful to have an alternate route in case we shut down the static announcement. Thanks, - j

3 7

BIRD 1.6.2 removes IPv6 kernel routes
by Robert Sander 21 Dec '16

21 Dec '16

Hi, I have an issue with BIRD 1.6.2 from http://bird.network.cz/debian/ on Debian jessie: When bird6 is running and I "ifup" an interface with a static IPv6 address the address is added but no IPv6 route in the associated network via that interface. When bird6 is not running everything works. It looks like bird6 1.6.2 is eating IPv6 routes set by the kernel. I have not encountered this issue with the IPv4 bird daemon. After downgrading to bird 1.4.5 from Debian jessie everything works as expected. What information do you need? Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

3 5

LSA ID collision issue is seen with OSPF stub-networks configured and BIRD is acting as ABR
by naveen chowdary Yerramneni 13 Dec '16

13 Dec '16

Hi, *Issue Description*: LSA ID collision issue is seen with OSPF *stub-networks* configured and BIRD is acting as ABR *BIRD OSPF configuration*: · Part of 2 areas (say, area-0 and area-100) · Stub-networks are configured in area-0 *Code Flow*: 1. Stubnets are advertised to area-0 by generating router LSA ( LSA_T_RT). o ospf_disp() -> ospf_update_topology() -> ospf_originate_rt_lsa()->ospf_ originate_lsa() 2. Now, stubnets are added to top graph table (p->gr) with LSA type LSA_T_RT 3. When creating routing table, these stubnets are added to FIB ( p->rtf). o ospf_disp() -> ospf_rt_spf() -> ospf_rt_spfa() -> spfa_process_rt() -> add_network() -> ri_install_net() 4. When BIRD is acting as ABR then, walk through FIB(p->rtf) and send summary LSA (LSA_T_SUM_NET) with LSA mode as LSA_M_RTCALC. Also, nf pointer is set (stores fib node address) in top_hash_entry. o ospf_disp() -> ospf_rt_abr2() -> check_sum_net_lsa() -> ospf_originate_sum_net_lsa() ->ospf_originate_lsa() 5. Now, stubnets are added to top graph table (p->gr) with LSA type LSA_T_SUM_NET 6. Stubnets are removed from FIB(p->rtf) o ospf_disp() -> rt_sync() -> fib_delete() 7. Now, stubnets entries are still present in top graph table (Note: fib_delte() doesn't free the node, it just moves the fib node to free pool, fib_node pointer is still valid) 8. With any change in network, ospf_rt_spf()is called. In ospf_rt_reset(), LSA mode is updated fromLSA_M_RTCALC to LSA_M_STALE. 9. Again, steps 3-6 are repeated. In step-3, fib node pointer is changed and in step-4, fib node pointer comparison fails in ospf_originate_lsa()which is leading to LSA id collision. *Issue is resolved with below code change. *Please review the change and provide your comments. Also, please let me know if any other information is required. diff -rupN bird/proto/ospf/topology.c bird_modified/proto/ospf/topology.c --- bird/proto/ospf/topology.c 2016-11-28 05:14:19.582761752 -0800 +++ bird_modified/proto/ospf/topology.c 2016-11-28 05:14:01.270761752 -0800 @@ -278,7 +278,7 @@ ospf_originate_lsa(struct ospf_proto *p, if (!SNODE_VALID(en)) s_add_tail(&p->lsal, SNODE en); - if (!en->nf || !en->lsa_body) + if (!en->nf || !en->lsa_body || en->mode == LSA_M_STALE) en->nf = lsa->nf; Thanks, Naveen

2 3

BGP large community duplicates
by Matt Griswold 02 Dec '16

02 Dec '16

>From Pierky's testing [0], Bird isn't removing received duplicates. Is anyone working on a patch for that? Otherwise I can take a look at it when I have time. Cheers [0] https://github.com/pierky/bgp-large-communities-playground/blob/master/test…

2 2

BIRD, Route Source and BSD
by Jean-Baptiste COUPIAC 30 Nov '16

30 Nov '16

Hello list, I'm a new in Bird word :). I'm working on a Bird mock-up. I'm actually blocked on OSPF filters. OSPF conf for First Router: *protocol ospf OSPF {* * import filter NFRANCE_OSPF_IN;* * export filter NFRANCE_OSPF_OUT;* * rfc1583compat yes;* * area 0 {* * interface "xn1" {* * type broadcast;* * };* * interface "xn2" {* * stub;* * };* * };* *};* OSPF conf for Second Router: *protocol ospf OSPF {* * import filter NFRANCE_OSPF_IN;* * export filter NFRANCE_OSPF_OUT;* * rfc1583compat yes;* * area 0 {* * interface "xn1" {* * type broadcast;* * };* * interface "xn2" {* * stub;* * };* * };* *};* Filters: *filter NFRANCE_OSPF_IN {* * if net ~ [80.247.224.0/20{24,32} <http://80.247.224.0/20{24,32}>] && (source ~ [ RTS_OSPF_EXT1, RTS_OSPF_EXT2 ])* * then* * {* * print net, " is accepted => OSPF_IN Public Nfrance";* * accept;* * }* * if net ~ [0.0.0.0/0{30,30} <http://0.0.0.0/0{30,30}>] && (source ~ [ RTS_OSPF_EXT1, RTS_OSPF_EXT2 ])* * then* * {* * print net, " is accepted => OSPF_IN Interco /30";* * accept;* * }* * else* * {* * print net, " is rejected => non OSPF_IN compliant";* * reject;* * }* * }* 80.247.227.2/24 is installed on Router 1, xn2 interface, Export network 80.247.227.0/24 on router 1 is ok but Import on the another router is KO. Indeed, If I use the condition: *if net ~ [80.247.224.0/20{24,32} <http://80.247.224.0/20{24,32}>] && (source ~ [ RTS_OSPF_EXT1, RTS_OSPF_EXT2 ])* 80.247.227.0/24 is rejected by the OSPF neighbor filter rule* NFRANCE_OSPF_IN* 2016-11-25 16:31:28 <INFO> 80.247.227.0/24 is rejected => non OSPF_IN compliant If I use the condition: *if net ~ [80.247.224.0/20{24,32} <http://80.247.224.0/20{24,32}>] *without *&& (source ~ [ RTS_OSPF_EXT1, RTS_OSPF_EXT2 ])* 80.247.227.0/24 is accepted by the OSPF neighbor filter rule* NFRANCE_OSPF_IN* 2016-11-25 16:42:18 <INFO> 80.247.227.0/24 is accepted => OSPF_IN Public Nfrance And when I check the bird route when network is accepted, I can see "OSPF" bird> show route 0.0.0.0/0 via 192.168.0.254 on xn0 [kernel1 16:35:00] * (10) 192.168.0.221/32 dev lo0 [kernel1 16:35:00] * (10) *80.247.227.0/24 <http://80.247.227.0/24> via 172.16.51.4 on xn1 [OSPF 16:42:18] * I (150/20) [192.168.0.223]* 172.16.51.1/32 dev lo0 [kernel1 16:35:00] * (10) bird> So I don't understand why *&& (source ~ [ RTS_OSPF_EXT1, RTS_OSPF_EXT2 ]) *does not match when the rule is added to my filter ? I use FreeBSD 10, Is there an issue on FBSD regarding RTS_* ? __ *Jean-Baptiste COUPIAC*

2 2

IS-IS ?
by Damien Clabaut 29 Nov '16

29 Nov '16

Hello, Do you have any future plans to implement the IS-IS routing protocol in Bird ? Regards, -- Damien Clabaut Network Engineer OVH.pl

3 2

Linux 'local' table (255) import into BIRD?
by Eric Vyncke (evyncke) 25 Nov '16

25 Nov '16

Hello, I am trying to import 'local' routes from the kernel into Bird without any success... The route is installed as: "/sbin/ip -6 route add local 2001:db8:cafe:babe::/64 dev lo" (it allows the host to reply/answer to any address in this prefix :-)) My bird6.conf is: protocol direct { interface "lo"; } # Table main is 254 # Table local is 255 protocol kernel { debug all; learn; persist; scan time 10; import all; export all; kernel table 255; } The log shows an attempt to import a connected route but not the 'local' one 2016-11-25 11:37:59 <TRACE> kernel1 < interface lo goes up 2016-11-25 11:37:59 <TRACE> kernel1 < interface eth0 goes up 2016-11-25 11:37:59 <TRACE> kernel1 < interface eth1 goes up 2016-11-25 11:37:59 <TRACE> kernel1: State changed to up 2016-11-25 11:37:59 <TRACE> kernel1: Scanning routing table 2016-11-25 11:37:59 <TRACE> kernel1: Pruning table master 2016-11-25 11:37:59 <TRACE> kernel1: Pruning inherited routes 2016-11-25 11:38:00 <TRACE> kernel1 < rejected by protocol 2001:db8:f00:beef::/64 dev eth1 2016-11-25 11:38:05 <TRACE> kernel1 < rejected by protocol 2001:db8:f00:beef::/64 dev eth1 2016-11-25 11:38:09 <TRACE> kernel1: Scanning routing table 2016-11-25 11:38:09 <TRACE> kernel1: Pruning table master 2016-11-25 11:38:09 <TRACE> kernel1: Pruning inherited routes Assistance will be welcome (and I did google a lot) -éric

4 6

BGP withdraw update on configuration reload
by Robert Sander 21 Nov '16

21 Nov '16

Hi, I experience the following behaviour with BIRD 1.6.2: 1. Change the config file 2. birdc configure 3. BIRD sends out an UPDATE message to its BGP peer to withdraw all prefixes learned via OSPF (see screenshot) 4. a second UPDATE message then contains all prefixes that should be announced according to the filters Where does this magic in step 3 come from? Why are prefixes getting leaked to the BGP peer that should not (even in a withdraw update)? Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 1