October 2012 - Bird-users

Does Bird accept configuration changes using the command line?
by 3.listas＠adminlinux.com.br 14 Nov '12

14 Nov '12

Hi, I have a network of ~ 200 servers with Quagga routers in the network core. I'm evaluating the impact of using the Bird in my routers and I have a question. In Quagga the administrator can change the configuration using a command line. For example, I have a shell script that changes the metric of a route in specific cases. Does Bird allow something similar? Does Bird accept configuration changes using the command line? Thanks -- Thiago Henrique www.adminlinux.com.br

3 4

BGP not starting
by Thomas St-Pierre 01 Nov '12

01 Nov '12

Hi, I'm a new BIRD user so I may be missing something, if so please forgive me. I created a simple config for an ibgp neighbor: template bgp rr_client { local as XXXXX; rr client; import all; export all; } protocol bgp R1 from rr_client { neighbor 172.19.242.51 as XXXXX; } The other end is a cisco router with a similarly simple config. However when I start up bird I get "Waiting for 172.19.242.51 to become my neighbor", and nothing ever happens. bird doesn't start listening on 179 either. For information, both bgp endpoints are in the same /24 subnet (ie directly connected). However if I add multihop then it comes up and everything's great. Is there a reason why I have to use multi hop when the devices are on the same lan? Thanks! Thomas

2 2

./configure error
by Phantom of the Opera 30 Oct '12

30 Oct '12

Hi, I'm trying to compile it on Max OS X ./configure checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for library containing clock_gettime... no checking build system type... i386-apple-darwin12.2.0 checking host system type... i386-apple-darwin12.2.0 checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking what CFLAGS should we use... -g -O2 -Wall -Wstrict-prototypes -Wno-parentheses -Wno-pointer-sign checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for flex... flex checking for bison... bison checking for gm4... gm4 configure: error: Cannot determine correct system configuration. Please use --with-sysconfig to set it manually. --- LLVM-GCC: build 2336 Clang: 4.1 build 421 Best Regards Stefan

6 6

Problem with Export Filter in OSPF
by Wendler, Daniel 25 Oct '12

25 Oct '12

Hello, i'm new to bird and try to setup an OSPF Setup with 4 instances of bird on Linux Systems. The used version is 1.3.8 installed trough the Debian Squeeze Repo provided by bird.network.cz. At the moment i tried to establish an export filter for OSPF, and it seems, that it isn't working at all. Same filter works best as an import filter: filter notrans { if net ~ [ 10.110.1.0/24+ ] then reject; accept; } I want this net (and all subnets) not exported to other nodes in the OSPF Areas. I tried to test the filter on the system where i will export some routes. Without the filter (import all;) i got this (filtered the interface names): 172.27.129.80/28 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.129.64/28 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.129.128/26 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.131.0/28 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.131.64/27 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.131.192/26 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.129.48/28 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.68.0/24 dev [transospf 18:15] * I (150/10) [10.110.1.118] 10.110.1.64/26 dev [transospf 18:52] * I (150/10) [10.110.1.118] << net is there 10.110.1.128/26 dev [transospf 18:52] * I (150/10) [10.110.1.118] << net is there 172.27.128.96/27 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.128.224/29 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.129.32/28 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.9.0/25 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.12.0/24 dev [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.13.0/24 dev [transospf 18:15] * I (150/10) [10.110.1.118] With the filter (import filter notrans;) i got: 172.27.129.80/28 dev as-doritest [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.129.64/28 dev as-dorilive [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.129.128/26 dev as-pmppu [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.131.0/28 dev im-cumulus [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.131.64/27 dev im-coback [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.131.192/26 dev im-misc [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.129.48/28 dev as-im-afadb [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.68.0/24 dev as-pg [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.128.96/27 dev as-immo-dwh [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.128.224/29 dev as-pmptu [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.129.32/28 dev as-im-afaweb [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.9.0/25 dev as-immo-test [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.12.0/24 dev as-immo-web [transospf 18:15] * I (150/10) [10.110.1.118] 172.27.13.0/24 dev as-immo-dbapp [transospf 18:15] * I (150/10) [10.110.1.118] As you can see, both nets are filtered, so i think the filter works as i expected but when i use this filter in export and look on another node i got: 172.27.129.80/28 via 10.110.1.178 on eth1 [transospf 18:20] ! IA (150/20) [10.110.1.118] 172.27.129.64/28 via 10.110.1.178 on eth1 [transospf 18:20] ! IA (150/20) [10.110.1.118] 172.27.129.128/26 via 10.110.1.178 on eth1 [transospf 18:20] * IA (150/20) [10.110.1.118] 172.27.131.0/28 via 10.110.1.178 on eth1 [transospf 18:20] * IA (150/20) [10.110.1.118] 172.27.131.64/27 via 10.110.1.178 on eth1 [transospf 18:20] ! IA (150/20) [10.110.1.118] 172.27.131.192/26 via 10.110.1.178 on eth1 [transospf 18:20] ! IA (150/20) [10.110.1.118] 172.27.129.48/28 via 10.110.1.178 on eth1 [transospf 18:20] ! IA (150/20) [10.110.1.118] 172.27.68.0/24 via 10.110.1.178 on eth1 [transospf 18:20] * IA (150/20) [10.110.1.118] 10.110.1.64/26 via 10.110.1.178 on eth1 [transospf 18:20] * IA (150/20) [10.110.1.118] << this should not happen i think! 10.110.1.128/26 dev eth1 [transospf 18:20] * I (150/10) [10.110.1.118] 172.27.128.96/27 via 10.110.1.178 on eth1 [transospf 18:20] ! IA (150/20) [10.110.1.118] 172.27.128.224/29 via 10.110.1.178 on eth1 [transospf 18:20] * IA (150/20) [10.110.1.118] 172.27.129.32/28 via 10.110.1.178 on eth1 [transospf 18:20] ! IA (150/20) [10.110.1.118] 172.27.9.0/25 via 10.110.1.178 on eth1 [transospf 18:20] * IA (150/20) [10.110.1.118] 172.27.12.0/24 via 10.110.1.178 on eth1 [transospf 18:20] ! IA (150/20) [10.110.1.118] 172.27.13.0/24 via 10.110.1.178 on eth1 [transospf 18:20] ! IA (150/20) [10.110.1.118] You can see, away from the scope link rooute i got the second 10.110 Network. In my eyes this schould not happen when the filter is applied. Did I miss something? Maybe someone could help me with this? Greetings Daniel Wendler

2 4

upgrade 1.2.4 - 1.3.1 reverted
by Arjan Filius 24 Oct '12

24 Oct '12

Hello, upgraded from bird 1.2.4 to bird 1.3.1 last weekend, but needed to revert due to complaints from high bgp traffic to bgpmon.net and 100% cpu load on a 2x bird bgp routers setup connected with iBGP. Did some research, and noticed a high bgp traffic situation on the iBGP sessions (about 10.000 bgp packets in 1.7 second) Based on graph statistics, i noticed a irregular traffic on the trans-ip's as well (noticed after rollback in statistical graphs) In the logging (mostly on the first bgp router) , i noticed quite some messages (33414 in ~12h) like: 29-05-2011 10:57:49 <WARN> Next hop address X.X.X.242 resolvable through recursive route for X.X.X.0/24 29-05-2011 10:57:49 <WARN> Next hop address Y.Y.35.194 resolvable through recursive route for Y.Y.32.0/19 29-05-2011 10:57:52 <WARN> Next hop address X.X.X.241 resolvable through recursive route for X.X.X.0/24 29-05-2011 10:57:52 <WARN> Next hop address X.X.X.242 resolvable through recursive route for X.X.X.0/24 29-05-2011 10:57:55 <WARN> Next hop address Y.Y.35.194 resolvable through recursive route for Y.Y.32.0/19 29-05-2011 10:57:55 <WARN> Next hop address X.X.X.241 resolvable through recursive route for X.X.X.0/24 29-05-2011 10:57:55 <WARN> Next hop address X.X.X.242 resolvable through recursive route for X.X.X.0/24 These are the subnets of the upstream trans-ip links of it's neigbor router On the second (neighbor) bgp router, noticed only such 15 recursive messages I had those upstream trans-ip interface IP's manually added once to the bird.conf with a "protocol static" definition with a subnet of /32. I thought this might be the problem, and wel, disabled those static trans-ip interface routes, except i forgot one. Noticed a lower CPU afterwards, but problem persisted, and i reverted to 1.2.4. Later i noticed i missed one static route to disable, but no time left to upgrade and test again. I think i should have looked at the recursive routes in bird, but i didn't. Does one know what was going on here, and what to do to prevent it when executing another upgrade? I created a 10.000 packet tcpdump capture (full size) of an iBGP session, in case somone would like to look at it. Regards, Arjan Filius -- Arjan Filius mailto:iafilius@xs4all.nl

4 7

Problem importing routes from kernel
by Tom Beecher 19 Oct '12

19 Oct '12

Good day. I'm new to BIRD, and am having an issue that's hopefully a simple fix. I'm running bird 1.2.5-1 on Debian, installed via package. My end goal is to use the BIRD process as a RTBH trigger via BGP. Currently, I'm unable to get BIRD to import kernel routes into the BIRD process, aside from the system default route. Interaction with the kernel definitely works; when I peer up with my BGP neighbor, our edge router with public BGP routes, they import and show up in the kernel route table without a problem. Here's my route table, and relevant sections of the BIRD config, and outputs from birdc. Thanks in advance for any assistance. root@genericsystemsimage:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.16.100.100 * 255.255.255.255 UH 0 0 0 eth0 207.251.204.0 * 255.255.255.240 U 0 0 0 eth0 default host-10.204-251 0.0.0.0 UG 0 0 0 eth0 root@genericsystemsimage:~# protocol kernel { learn; # Learn all alien routes from the kernel persist; # Don't remove routes on bird shutdown scan time 20; # Scan kernel routing table every 20 seconds import all; # Default is import all export all; # Default is export none } protocol device { scan time 10; # Scan interfaces every 10 seconds } protocol bgp test { description "Test peer"; local as XXXX; neighbor A.B.C.D as XXXX; import none; export all; } bird> show route 0.0.0.0/0 via 207.251.204.10 on eth0 [kernel1 16:57] * (10) bird> show protocols all name proto table state since info kernel1 Kernel master up 16:57 Preference: 10 Input filter: ACCEPT Output filter: ACCEPT Routes: 1 imported, 0 exported, 1 preferred Route change stats: received rejected filtered ignored accepted Import updates: 1 0 0 0 1 Import withdraws: 0 0 --- 0 0 Export updates: 1 1 0 --- 0 Export withdraws: 0 --- --- --- 0 -- Thomas Beecher II Senior Network Administrator LocalNet Corp. CoreComm Internet Services tbeecher at localnet dot com

3 5

OSPF virtual link segfault in 1.3.7 (wheezy)
by Kristian Lyngstol 15 Oct '12

15 Oct '12

Greetings. I just started playing with bird yesterday (my first endeavour into dynamic routing). I got OSPF set up nicely, but wanted to use multiple areas. I'm using OPSFv3(bird6/IPv6). There are essentially two issues I'm having: 1. "It doesn't work." This is probably just because I've not configured it correctly yet and is somewhat secondary. 2. Whenever I throw 'virtual link' in an area, bird segfaults on startup. I sort of assume my configuration has a logical flaw which is triggering it, but I've yet to see what. The bird6 config looks like this: ---- quote ---- log syslog all; router id 10.0.0.1; debug protocols all; protocol kernel { learn; # Learn all alien routes from the kernel persist; # Don't remove routes on bird shutdown scan time 20; # Scan kernel routing table every 20 seconds # import none; # Default is import all export all; # Default is export none # kernel table 5; # Kernel table to synchronize with (default: main) } protocol device { scan time 10; # Scan interfaces every 10 seconds } protocol static { } protocol ospf MyOSPF { area 0.0.0.0 { stub no; interface "eth2"; }; area 0.0.0.2 { stub yes; interface "eth1"; virtual link 10.30.0.1; }; } protocol radv { interface "eth1"; } ---- end quote ---- It's worth noting that the above config was just set up to trigger this. 10.30.0.1 is a not connected to the backbone, and that's where I originally ran into this when I tried to figure out how to get a router not directly connected to the backbone to play along with the rest... This is all within a VM. I've tried some other variations of the same setup and it still breaks the moment I mention 'virtual link'. Again, I assume this config is wrong, but it obviously shouldn't segfault anyway. Here's the relevant syslog entries with timestamps trimmed: ---- start quote ---- bird6: Started bird6: device1: State changed to up bird6: kernel1: Connected to table master bird6: kernel1: State changed to up bird6: static1 < interface lo goes up bird6: static1 < interface eth1 goes up bird6: static1 < interface eth0 goes up bird6: static1: State changed to up bird6: MyOSPF: Connected to table master bird6: MyOSPF < interface lo goes up bird6: MyOSPF < primary address ::1/128 on interface lo added bird6: MyOSPF < interface eth1 goes up bird6: MyOSPF < primary address 2a02:fe0:cf16:79::/64 on interface eth1 added bird6: MyOSPF < secondary address fe80::/64 on interface eth1 added bird6: MyOSPF: Adding interface eth1 (IID 0) to area 0.0.0.2 bird6: MyOSPF < interface eth0 goes up bird6: MyOSPF < primary address 2a02:fe0:cf16:78::/64 on interface eth0 added bird6: MyOSPF < secondary address fe80::/64 on interface eth0 added bird6: MyOSPF: State changed to up bird6: radv1 < interface lo goes up bird6: radv1 < primary address ::1/128 on interface lo added bird6: radv1 < interface eth1 goes up bird6: radv1: Adding interface eth1 bird6: radv1 < primary address 2a02:fe0:cf16:79::/64 on interface eth1 added bird6: radv1 < secondary address fe80::/64 on interface eth1 added bird6: radv1 < interface eth0 goes up bird6: radv1 < primary address 2a02:fe0:cf16:78::/64 on interface eth0 added bird6: radv1 < secondary address fe80::/64 on interface eth0 added bird6: radv1: State changed to up bird6: kernel1: Scanning routing table bird6: kernel1: Pruning table master bird6: kernel1: Pruning inherited routes bird6: radv1: Event Init on eth1 bird6: MyOSPF: Changing state of iface eth1 from down to waiting bird6: MyOSPF: Scheduling router-LSA origination for area 0.0.0.2 bird6: MyOSPF: HELLO packet sent via eth1 bird6: MyOSPF: Scheduling link-LSA origination for iface eth1 bird6: radv1: Timer fired on eth1 bird6: radv1: Sending RA via eth1 bird6: MyOSPF: Originating router-LSA for area 0.0.0.2 bird6: MyOSPF: Scheduling routing table calculation bird6: MyOSPF: Originating router prefix-LSA for area 0.0.0.2 bird6: MyOSPF: Originating link-LSA for iface eth1 kernel: [127469.292849] bird6[5956]: segfault at 28 ip 00007f85aab58a9b sp 00007fffece33910 error 4 in bird6[7f85aab2b000+65000] ---- quote end ---- This is all running on a Debian Wheezy VM (on a debian wheezy host, if it matters). I did a backtrace of the segfault too, and it's a fairly straight forward null pointer deref: ---- quote ---- (gdb) run -d -c /etc/bird6.conf Starting program: /usr/sbin/bird6 -d -c /etc/bird6.conf [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x0000555555581a9b in ospf_lsa_flooding_allowed (lsa=0x7fffffffe8c0, domain=2, ifa=0x5555557ca5e0) at ../../../proto/ospf/lsupd.c:122 122 return ifa->iface->index == domain; (gdb) bt #0 0x0000555555581a9b in ospf_lsa_flooding_allowed (lsa=0x7fffffffe8c0, domain=2, ifa=0x5555557ca5e0) at ../../../proto/ospf/lsupd.c:122 #1 0x0000555555581b65 in ospf_lsupd_flood (po=0x5555557c8f20, n=0x0, hn=0x0, hh=0x7fffffffe8c0, domain=2, rtl=1) at ../../../proto/ospf/lsupd.c:172 #2 0x000055555557a957 in originate_link_lsa (ifa=0x5555557ca810) at ../../../proto/ospf/topology.c:1219 #3 0x000055555557a9dc in update_link_lsa (ifa=0x5555557ca810) at ../../../proto/ospf/topology.c:1235 #4 0x0000555555578040 in area_disp (oa=0x5555557ca2f0) at ../../../proto/ospf/ospf.c:455 #5 0x0000555555578098 in ospf_disp (timer=<optimized out>) at ../../../proto/ospf/ospf.c:475 #6 0x0000555555597de8 in tm_shot () at io.c:374 #7 io_loop () at io.c:1560 #8 0x000055555555c065 in main (argc=<optimized out>, argv=<optimized out>) at main.c:699 (gdb) frame 0 #0 0x0000555555581a9b in ospf_lsa_flooding_allowed (lsa=0x7fffffffe8c0, domain=2, ifa=0x5555557ca5e0) at ../../../proto/ospf/lsupd.c:122 122 return ifa->iface->index == domain; (gdb) display ifa->iface 1: ifa->iface = (struct iface *) 0x0 (gdb) display *iface (gdb) display *ifa 2: *ifa = {n = {next = 0x5555557ca810, prev = 0x5555557c90d0}, iface = 0x0, addr = 0x0, oa = 0x5555557ca040, cf = 0x5555557c58c0, pool = 0x5555557ca580, sk = 0x0, neigh_list = {head = 0x5555557ca628, null = 0x0, tail = 0x5555557ca620}, cost = 0, waitint = 40, rxmtint = 5, pollint = 0, deadint = 40, vid = 169738241, vip = {addr = {0, 0, 0, 0}}, vifa = 0x0, voa = 0x5555557ca2f0, inftransdelay = 1, helloint = 10, drip = {addr = {0, 0, 0, 0}}, bdrip = {addr = {0, 0, 0, 0}}, drid = 0, bdrid = 0, rt_pos_beg = 0, rt_pos_end = 0, px_pos_beg = 0, px_pos_end = 0, dr_iface_id = 0, instance_id = 0 '\000', type = 4 '\004', strictnbma = 0 '\000', stub = 0 '\000', state = 0 '\000', wait_timer = 0x0, hello_timer = 0x5555557ca720, poll_timer = 0x0, net_lsa = 0x0, orignet = 0, origlink = 0, link_lsa = 0x0, pxn_lsa = 0x0, fadj = 0, nbma_list = { head = 0x5555557ca6f8, null = 0x0, tail = 0x5555557ca6f0}, priority = 0 '\000', ioprob = 0 '\000', sk_dr = 0 '\000', marked = 0 '\000', rxbuf = 0, check_link = 0 '\000', ecmp_weight = 0 '\000'} (gdb) quit ---- quote end ---- Hopefully someone can help me out, otherwise I suppose I'll dig into it this weekend. I did take a quick look at the diff between 1.3.7 and master, but the changes seemed somewhat insignificant for this specific issue. Either way, I'll build it from the master branch tomorrow to test. - Kristian

2 1

Feature request: sort addresses/networks
by Ruben Laban 11 Oct '12

11 Oct '12

Hello bird-maintainers, I'd like to propose a cosmetic feature request: The sorting of addresses/networks listed in "show ospf state" (and possibly similar commands as well). Currently networks are listed semi-random it seems, like so: router 10.0.0.1 distance 0 router 10.0.0.2 stubnet 192.168.1.0/24 stubnet 192.168.5.0/24 stubnet 192.168.3.0/24 I'd like it to display the following instead: router 10.0.0.1 distance 0 router 10.0.0.2 stubnet 192.168.1.0/24 stubnet 192.168.3.0/24 stubnet 192.168.5.0/24 This eases the finding of a given network in sometimes rather largish lists. Regards, Ruben Laban

1 1

OSPF: External routes (ABR vs ASBR)
by Ruben Laban 11 Oct '12

11 Oct '12

Hi list, I'm trying to figure out how bird distinguishes between imported routes that are shown as "external" route directly under the router's id (in "show ospf state") and those listed under the "other ASBRs" header. I have different boxes showing different behavior. I just can't seem to pinpoint the reason for a route show up under the "other ASBRs" header. Regards, Ruben Laban

2 4

Repeated log OSPF LSA disappeared
by Internet Expert s.r.o. - Žichovský Pavel 09 Oct '12

09 Oct '12

Hi, I'm new with Bird. Currently we have deployed it on one router for OSPF. Everything works fine, until one interface on other router in OSPF network went down.

4 3