- Bird-users - Mailing Lists

inject more specific route
by Thilo Bangert 03 Jul '13

03 Jul '13

Hi, basically i have a setup where bird gets a default route from a peer and i want bird to inject a more specific route into the local kernel table. is this possible? any hints on how to achieve this? thanks kind regards Thilo

2 1

show route filtered
by Joe Wooller 01 Jul '13

01 Jul '13

Hey All, I sent this to the euro-ix bird list, with little response. It was suggested that I send it here. I am a little confused as to what show route filtered is meant to do. I was under the impression it would show filtered routes. <SNIP> If BIRD is configured to keep filtered routes (see import keep filtered option), you can show them instead of routes by using filtered switch. </SNIP> I have set; import keep filtered; in my template. Unfortunately show route filtered delivers nothing. Am I missing something? If I do: show route table master protocol R_AS1234x1 I can see only the routes that are allowed to pass (not filtered). If i do: show route protocol R_AS1234x1 I see all routes include routes that get filtered out of the master table. But if I do bird> show route table master filtered bird> show route table master filtered protocol R_AS1234x1 bird> show route filtered bird> show route filtered protocol R_AS1234x1 I get nothing.. Here is an snippet of config; ## ## Protocol Templates ## template bgp IXP { local as ixasn; start delay time 10; debug { states, events }; mrtdump all; #import all; import keep filtered; export all; rs client; } template pipe PIPES { table master; mode transparent; } ## AS1234 - Peer1 table T_AS1234; filter bgp_in_AS1234 prefix set allnet; int set allasn; { if !(avoid_martians()) then reject; if (bgp_path.first != 1234 ) then reject; allasn = [ 1234 ]; if !(bgp_path.last ~ allasn) then reject; accept; } protocol pipe P_AS1234 from PIPES { description "Pipe for AS1234 - Peer1"; peer table T_AS1234; import filter bgp_in_AS1234; export where bgp_out(1234, false); } protocol bgp R_AS1234x1 from IXP { description "RIB for AS1234 - Peer1"; debug { states, events }; neighbour 1.2.3.4 as 1234; route limit 500; table T_AS1234; } If my understanding of how the filtered option works is completely wrong please let me know! Any help/advise would be greatly appreciated. Cheers Joe

2 1

infinite adding of ipv6 routes to kernel table which were recieved from ebgp peer and piped into kernel protocol
by Arnautov Artem 01 Jul '13

01 Jul '13

Hi we have problems on one of our router with bird6 and ebgp neighbors when we recieve ipv6 full view from ebgp neighbor and put it into separate table everything is OK when we pipe it into master table everything is OK when we enable export all ipv6 routes into kernel protocol strange things happens while trying to find out how many ipv6 routes were added trying to run command like ip -6 ro sh | wc -l we may sit and wait for a long time without any success if we looking for route count from bird6 console everything is ok but if we enable debug off route protocol we see messages like 26-06-2013 12:58:03 <TRACE> kernel: Scanning routing table 26-06-2013 12:58:03 <TRACE> kernel: 2001::/32: seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:200:900::/40: seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:200:c00::/40: seen ...... 26-06-2013 12:58:03 <TRACE> kernel: 2001:2b8:11::/48: already seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:2b8:15::/48: already seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:2b8:16::/48: already seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:2b8:17::/48: already seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:2b8:19::/48: already seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:2b8:20::/48: already seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:2b8:21::/48: already seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:2b8:22::/48: already seen 26-06-2013 12:58:03 <TRACE> kernel: 2001:2b8:25::/48: already seen ..... and then again and again and again same lines of data with "already seen" even if we define scan time 600 and restarting kernel protocol nothing changes with routes recieved from ibgp there are no such problems here is sample configuration router id xx.xx.xx.xx; define myas = ZZZZZ; protocol device device { scan time 10; } protocol kernel kernel { export all; import none; scan time 15; } protocol direct direct { export none; import none; } table T_ebgp; filter pipe_ebgp_in { preference = 500; accept; } filter pipe_ebgp_out { if (myas,client) ~ bgp_community then accept; reject; } protocol pipe P_ebgp_peer { description "EBGP peer Pipe to master table"; table master; mode transparent; peer table T_ebgp; import filter pipe_ebgp_in; export filter pipe_ebgp_out; } protocol bgp R_ebgp_peer { description "ebgp IPv6"; local as myas; neighbor 2001:xxx:x:xx::1 as XXX; import all; export all; next hop self; table T_ebgp; gateway direct; #disabled; } -- --- Арнаутов Артем ISP NetAssist +380 44 2398989

3 5

MPLS for bird
by Reza Mirzazadeh 26 Jun '13

26 Jun '13

hi i was looking for documents for bird-devel ( bird mpls ) but i couldn't find anything . i've installed bird-devel but i don't know how to config MPLS for it . is there any documentation for it ? i even don't know that MPLS is installed or not ! thanks in advance --

2 2

Testing framework
by Sam Russell 24 Jun '13

24 Jun '13

Is there a set of unit tests for BIRD somewhere? I don't know where I'd start building them, but I'm happy to do the legwork on the coding - unit testing will make it a lot easier to add new modules and guarantee the functionality of existing ones.

2 3

RIPng advertisement hop count 1 (should be 255 per RFC)
by Simon Dickhoven 24 Jun '13

24 Jun '13

Hi, I just started experimenting with BIRD for an IPv6 deployment. I am using Vyatta VC6.6R1 router VMs on either side of my BIRD VM (which runs on a customized Debian Squeeze release with kernel 3.3.1). I installed bird/bird6 1.3.7 from the squeeze-backports repository. Here my setup. Lab Net --- Vyatta --- BIRD on Debian --- Vyatta --- Stub Net Anyway, I don't have any problems with my configs or anything like that. My problem is that Vyatta's ripngd (part of Quagga) complains about an RFC violation when it receives RIPng advertisements from BIRD: Jun 14 21:43:40 vyatta ripngd[1682]: RIPng packet comes with non 255 hop count 1 from fe80::20c:29ff:fef8:cbc5 I looked at the source code in rip.c and see this line: rif->sock->ttl = 1; which is the only reference I can find to TTL/Hop Count. So I'm guessing this is the culprit. The latest source code (1.3.10) is identical in this respect. RFC 2080 states [...] As an additional check, periodic advertisements must have their hop counts set to 255, and inbound, multicast packets sent from the RIPng port (i.e. periodic advertisement or triggered update packets) must be examined to ensure that the hop count is 255. [...] The use of the term "must" leads me to believe that this is not optional and is therefore required for RFC-compliance. There seems to be no such requirement for RIP (v1/v2) so simply changing the source code to indiscriminately set the TTL to 255 is probably not the right thing to do. Have others encountered this problem and is there possibly a patch or something for getting RFC-compliance and hence interoperability with Vyatta/Quagga(ripngd)? Thanks. - Simon

2 6

netmpls/mpls.h
by Reza Mirzazadeh 23 Jun '13

23 Jun '13

hi . i was wondering why bird-devel20120323 dos not install in freebsd 9.1 release ! i install it form standard ports ! but i get some message like these no such file or directory /netmpl/mpls.h then i downloaded mpls.h from here https://github.com/toddfries/OpenBSD-sys-patches/blob/master/netmpls/mpls.h but it didn't help me for fixing ! what should do i ? thanks in advance

1 0

Propagating /32 from OSPF to BGP
by Michael Ludvig 20 Jun '13

20 Jun '13

Hi we've got a private AS with two uplinks to our ISP, and we've got a number of subnets that we advertise. Now we got a new assignment and it doesn't work as expected. Here is the situation: x.x.74.113 x.x.74.114 [DMZ1_box_1] || [DMZ1_GW] -- OSPF -- [GW_1] -- OSPF -- [GW_2] -- OSPF -- ... x.x.24.227 | | BGP BGP | | ISP_rtr_1 ISP_rtr_2 \ / ISP & Internet Now if I advertise the new subnet /29 (or up to /31) from DMZ1_GW it gets propagated to both BGPs and the ISP correctly routes the traffic to GW_1 as it's closer to the box. However if I advertise the IP/32 from DMZ1_GW then for some reason the traffic is routed from Internet to GW_2 first. ISP confirmed they accept up to /32 from us. This is the relevant output from GW_1: GW_1 ~ # birdc show route protocol ospf_eit | grep ^x.x.74 BIRD 1.3.8 ready. x.x.74.114/32 via 172.31.253.32 on tunVpnCust [ospf_eit 11:44] * E2 (150/1/10000) [x.x.24.227] x.x.74.112/31 via 172.31.253.32 on tunVpnCust [ospf_eit 11:44] * E2 (150/1/10000) [x.x.24.227] GW_1 ~ # birdc show route export bgp_isp | grep ^x.x.74 BIRD 1.3.8 ready. x.x.74.114/32 via 172.31.253.32 on ifDmz1 [ospf_eit 11:44] * E2 (150/1/10000) [x.x.24.227] x.x.74.112/31 via 172.31.253.32 on ifDmz1 [ospf_eit 11:44] * E2 (150/1/10000) [x.x.24.227] This is the relevant output from GW_2: GW_2 ~ # birdc show route protocol ospf_eit| grep ^x.x.74 BIRD 1.3.8 ready. x.x.74.114/32 via 172.31.253.1 on tunO2Oorc4 [ospf_eit 11:44] * E2 (150/11/10000) [x.x.24.227] x.x.74.112/31 via 172.31.253.1 on tunO2Oorc4 [ospf_eit 11:44] * E2 (150/11/10000) [x.x.24.227] GW_2 ~ # birdc show route export bgp_isp | grep ^x.x.74 BIRD 1.3.8 ready. x.x.74.114/32 via 172.31.253.1 on tunO2Oorc4 [ospf_eit 11:44] * E2 (150/11/10000) [x.x.24.227] x.x.74.112/31 via 172.31.253.1 on tunO2Oorc4 [ospf_eit 11:44] * E2 (150/11/10000) [x.x.24.227] As it is now a ping from outside to x.x.74.113 (that's advertised as /31) goes to GW_1, which is correct and a ping to x.x.74.114 (that's advertised as /32) goes to GW_2, that's incorrect. How come? I can't see what am I doing wrong...? Any ideas? Thanks Michael

3 3

Not re-exporting learned OSPF routes
by Ryan Whelan 18 Jun '13

18 Jun '13

I feel like this should be simple, but I can't find what I'm looking for... I have a few of routers spread across the country in a full mesh running OSPF. 'Servers' and 'clients' connect to these 'routers' to connect to one another- each 'server' and 'client' run a basic bird instance they use to share a local address (X.X.X.X/32). The issue is some of the 'servers' connect to multiple 'routers' so if a link between 2 routers is down, OSPF tries to route though a server... ('servers' don't have ip forwarding on) In short, how do I make sure the 'servers' can run bird to update OSPF with their /32 address but not re-propagate routes they learn from OSPF (so as to not be considered for route selection by the routers)? Forgive me if this is basic question- it feels pretty basic. Reading the documents about filters, it looks like they apply purely to route evaluation between bird and the kernel routing table, they aren't evaluated when propagating routes to other OSPF neighbors. Thanks! ryan

3 7

Route withdrawn via pipe to another kernel table causes segfault crash
by Joel Mulkey 18 Jun '13

18 Jun '13

Hello, We are running BIRD v1.3.10 and are seeing an issue that is causing BIRD to crash. In this setup we're running one "core" router that's using a single routing table, an OSPF protocol, and 2 BGP protocols. That core router connects to 2 remote routers that are running one OSPF protocol, one BGP protocol, and using 2 routing tables (main and one other). The routing tables are connected via pipe, and they are both connected to Linux tables via the kernel protocols. The issue we're seeing is that when a route is withdrawn (we're only installing the default route) from the 2nd routing table on the remote routers it crashes BIRD with a segfault. This is typically caused by a loss in connectivity on the network that tears down the OSPF and BGP sessions. We tried a number of things to prevent the issue from happening. If we prevent either the pipe or kernel protocols from exporting routes then the issue does not occur. We also tried setting the pipe to opaque mode and that immediately causes a segfault on start up. This appears to be a bug with the kernel or pipe protocol, but I'm certainly no expert and would love some guidance if there's a workaround or error in my config. Below is the remote router config, and some snippits of the syslog with the segfaults. Thanks, Joel Mulkey function infrastructure() { if net = 10.99.0.4/32 then return true; if net ~ [10.2.0.0/30+] then return true; if net ~ [172.17.1.0/24+] then return true; if net ~ [172.17.2.0/24+] then return true; if net ~ [172.17.3.0/24+] then return true; if net ~ [172.17.4.0/24+] then return true; return false; } function default_only() { return net = 0.0.0.0/0; } filter table2_out_filter { if ! defined( krt_metric ) then accept; if krt_metric > 1 then reject; else accept; } filter ospf_out { if infrastructure() then accept; else reject; } filter bgp_out { if infrastructure() then reject; if ! defined( krt_metric ) then accept; if krt_metric > 19 then { bgp_local_pref = 90; accept; } else accept; } table table2; router id 10.99.0.4; log syslog all; debug protocols { states, routes, filters, interfaces }; protocol kernel kmain { learn; # Learn all alien routes from the kernel persist; # Don't remove routes on bird shutdown scan time 2; # Scan kernel routing table every 10 seconds import all; # Default is import all export all; # Default is export none preference 190; } protocol kernel ktable2 { persist; # Don't remove routes on bird shutdown scan time 2; # Scan kernel routing table every 2 seconds import none; # Default is import all export filter table2_out_filter; # Default is export none kernel table 100; # Kernel table to synchronize with (default: main) table table2; # connect to alternate BIRD table } # This pseudo-protocol watches all interface up/down events. protocol device { scan time 2; # Scan interfaces every 2 seconds } # Pipe protocol connects two routing tables... Beware of loops. # Connect table2 to main protocol pipe { mode transparent; peer table table2; export all; import none; } protocol ospf to_core_ospf { debug { events }; export filter ospf_out; import all; area 0.0.0.0 { stubnet 10.99.0.4/32; interface 10.2.0.2 { hello 1; retransmit 2; cost 10; dead 5; wait 4; type broadcast; }; }; } protocol bgp bgp_peer_1 { local as 64600; export filter bgp_out; import all; source address 10.99.0.4; next hop self; neighbor 10.99.0.1 as 64600; multihop 20; hold time 12; keepalive time 3; startup hold time 10; connect retry time 5; start delay time 5; error wait time 30, 120; } Jun 11 21:16:44 tunnel2 bird: bgp_peer_1: Error: Hold timer expired Jun 11 21:16:44 tunnel2 bird: bgp_peer_1: State changed to flush Jun 11 21:16:44 tunnel2 bird: bgp_peer_1 > removed [sole] 0.0.0.0/0 unreachable Jun 11 21:16:44 tunnel2 bird: pipe1 < removed 0.0.0.0/0 unreachable Jun 11 21:16:44 tunnel2 bird: pipe1 > removed [sole] 0.0.0.0/0 unreachable Jun 11 21:16:44 tunnel2 bird: ktable2 < removed 0.0.0.0/0 unreachable Jun 11 21:16:44 tunnel2 bird: kmain < removed 0.0.0.0/0 unreachable Jun 11 21:16:44 tunnel2 kernel: [ 769.220353] bird[4516]: segfault at 18 ip 00007ff0e8e44e26 sp 00007fffc45719f0 error 4 in bird[7ff0e8e3a000+5e000] Jun 11 21:27:09 tunnel2 bird: to_core_ospf: Scheduling routing table calculation Jun 11 21:27:09 tunnel2 bird: to_core_ospf: Neighbor 10.2.0.1 changes state from " loading" to " full". Jun 11 21:27:09 tunnel2 bird: to_core_ospf: Scheduling router-LSA origination for area 0.0.0.0 Jun 11 21:27:09 tunnel2 bird: to_core_ospf: Scheduling network-LSA origination for iface eth0 Jun 11 21:27:10 tunnel2 bird: bgp_peer_1: Error: Hold timer expired Jun 11 21:27:10 tunnel2 bird: bgp_peer_1: State changed to flush Jun 11 21:27:10 tunnel2 bird: to_core_ospf: Originating network-LSA for iface eth0 Jun 11 21:27:10 tunnel2 kernel: [ 1395.215433] bird[5318]: segfault at 18 ip 00007f6232c2ae26 sp 00007fff05713ea0 error 4 in bird[7f6232c20000+5e000] mode opaque causing immediate segfault on restart Jun 11 21:44:05 tunnel1 bird: kmain: Initializing Jun 11 21:44:05 tunnel1 bird: ktable2: Initializing Jun 11 21:44:05 tunnel1 bird: device1: Initializing Jun 11 21:44:05 tunnel1 bird: pipe1: Initializing Jun 11 21:44:05 tunnel1 bird: bgp_peer_1: Initializing Jun 11 21:44:05 tunnel1 bird: device1: Starting Jun 11 21:44:05 tunnel1 bird: device1: Connected to table master Jun 11 21:44:05 tunnel1 bird: device1: State changed to feed Jun 11 21:44:05 tunnel1 bird: kmain: Starting Jun 11 21:44:05 tunnel1 bird: kmain: Connected to table master Jun 11 21:44:05 tunnel1 bird: kmain: State changed to feed Jun 11 21:44:05 tunnel1 bird: ktable2: Starting Jun 11 21:44:05 tunnel1 bird: ktable2: Connected to table table2 Jun 11 21:44:05 tunnel1 bird: ktable2: State changed to feed Jun 11 21:44:05 tunnel1 bird: pipe1: Starting Jun 11 21:44:05 tunnel1 bird: pipe1: Connected to table master Jun 11 21:44:05 tunnel1 bird: pipe1: Connected to table table2 Jun 11 21:44:05 tunnel1 bird: pipe1: State changed to feed Jun 11 21:44:05 tunnel1 bird: to_core_ospf: Adding area 0.0.0.0 Jun 11 21:44:05 tunnel1 bird: bgp_peer_1: Starting Jun 11 21:44:05 tunnel1 bird: Started Jun 11 21:44:05 tunnel1 bird: device1: State changed to up Jun 11 21:44:05 tunnel1 bird: kmain: State changed to up Jun 11 21:44:05 tunnel1 bird: ktable2: State changed to up Jun 11 21:44:05 tunnel1 bird: pipe1: State changed to up Jun 11 21:44:05 tunnel1 bird: to_core_ospf: Adding interface eth0 (10.1.0.0/30) to area 0.0.0.0 Jun 11 21:44:05 tunnel1 bird: kmain > added [best] 172.16.4.0/24 via 172.16.4.2 on tun4 Jun 11 21:44:05 tunnel1 bird: kmain < rejected by protocol 172.16.4.0/24 via 172.16.4.2 on tun4 Jun 11 21:44:05 tunnel1 bird: pipe1 < added 172.16.4.0/24 via 172.16.4.2 on tun4 Jun 11 21:44:05 tunnel1 bird: pipe1 > added [best] 172.16.4.0/24 via 172.16.4.2 on tun4 Jun 11 21:44:05 tunnel1 bird: kvpn_output < added 172.16.4.0/24 via 172.16.4.2 on tun4 Jun 11 21:44:05 tunnel1 bird: pipe1 < rejected by protocol 172.16.4.0/24 via 172.16.4.2 on tun4 Jun 11 21:44:05 tunnel1 kernel: [ 2403.848692] bird[5450]: segfault at 18 ip 00007f0cc629f277 sp 00007fff33e14ed8 error 4 in bird[7f0cc6271000+5e000]

2 5