September 2011 - Bird-users

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

OSPF loading State
by Ryan Whelan 09 Jan '12

09 Jan '12

I have 2 linux machines connected to one another over the internet via a IPSec protected GRE tunnel. Each of them are running OSPF from bird 1.3.2. The issue is that one of them will not fully peer with the other, unless the other is started after the one with the issue. Is just stays in state 'loading' while the other machine will be in state 'full'. In other words, node 2 will only go to state 'full' if node 1 is started after node 2. If node 2 is started after node 1, it will sit in state 'loading' forever. Node 1 has no issues. Here is a log from the node that is failing to sync up (node 2): http://pastebin.com/ZjVcc1wB bird> show ospf neighbors axa0: Router ID Pri State DTime Interface Router IP 111.222.333.444 1 loading/ptp 00:13 tun10 172.31.255.255 bird> the config on both machines is identical protocol kernel { learn;; persist; scan time 20; export all; } protocol device { scan time 10; } protocol static { } protocol ospf axa0 { tick 1; rfc1583compat yes; area 0.0.0.0 { stub no; interface "tun*" { hello 5; retransmit 5; cost 10; transmit delay 5; dead 15; wait 50; type ptp; }; }; }

4 17

Make bird 1.3.2 failed
by Alexander V. Pen'kov 26 Oct '11

26 Oct '11

Good day! I have Centos 5.6 with all lastest updates(exec yum update). And i would like to install bird 1.3.2(bird 1.3.1 installed successfuly) but when i execute "make" it not successfuly done with result: make[2]: Leaving directory `/usr/src/bird-1.3.2/obj/client' gcc -o ../bird nest/all.o filter/all.o proto/bgp/all.o proto/ospf/all.o proto/pipe/all.o proto/rip/all.o proto/static/all.o conf/all.o lib/birdlib.a -lrt lib/birdlib.a(main.o): In function `drop_uid': /usr/src/bird-1.3.2/obj/lib/../lib/syspriv.h:49: undefined reference to `CAP_TO_MASK' /usr/src/bird-1.3.2/obj/lib/../lib/syspriv.h:49: undefined reference to `CAP_TO_MASK' /usr/src/bird-1.3.2/obj/lib/../lib/syspriv.h:49: undefined reference to `CAP_TO_MASK' /usr/src/bird-1.3.2/obj/lib/../lib/syspriv.h:49: undefined reference to `CAP_TO_MASK' collect2: ld returned 1 exit status make[1]: *** [../bird] Error 1 make[1]: Leaving directory `/usr/src/bird-1.3.2/obj' make: *** [all] Error 2 What is this problem? Thanks! -- Alexandre V. Pen'kov mailto:shurskiy@gmail.com Mobile: +7(916)591-9113

3 6

how to confirm which capabilities have been negotiated
by Eiichiro Watanabe 24 Oct '11

24 Oct '11

Hello, Do we have an appropriate command to show which BGP capabilities have been negotiated on bird after a peer has been established? Of course, I known I can recognize when I look into packets captured, or confirm it on the neighbor router by using "show ip bgp neighbor x.x.x.x" command (in the case of CiscoIOS). it wouldn't be smart. Thanks, eiichiro -- ################################################### Eiichiro Watanabe Internet Multifeed Co.

4 5

New release 1.3.2!
by Ondrej Filip 21 Oct '11

21 Oct '11

Hi! New version is ready! It includes mainly minor bugfixes and minor improvements all made by Santiago. We are working on packaging and other stuff. Changes: Version 1.3.2 o Allows run with restricted privileges. o Community list filter operation. o Fixes several problems in filter syntax: - Fixes several conflicts in the grammar. - Fixes a bug in (a..b, c) pair patterns. - Makes pair patterns orthogonal. - Allows term expressions in pair patterns without additional (). - Allows several comma separated values in switch cases. o Many bugfixes. Ondrej

9 17

Adding BuildRequires for RPM SPEC file
by Ang Way Chuang 10 Oct '11

10 Oct '11

Hi all, I thought that this may be useful. Anyway, is there any standard procedure to produce src.rpm from the git repository? I cannot find the src.rpm for bird-1.3.3-1. Thanks. Regards, Ang Way Chuang diff --git a/misc/bird.spec b/misc/bird.spec index 16aa682..030005f 100644 --- a/misc/bird.spec +++ b/misc/bird.spec @@ -10,6 +10,7 @@ Source2: birdc6 Buildroot: /var/tmp/bird-root Url: http://bird.network.cz Prereq: /sbin/chkconfig +BuildRequires: flex bison readline-devel ncurses-devel %description BIRD is dynamic routing daemon supporting IPv4 and IPv6 versions of routing

2 1

ERR when redistributing to OSPF NSSA
by Fedor Dikarev 02 Oct '11

02 Oct '11

Hello, I've got the problem: I'm trying to reditribute lo-address-es to ospf nssa area: > ifconfig lo0 > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 > options=3<RXCSUM,TXCSUM> > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > inet 81.19.70.17 netmask 0xffffffff > inet 81.19.70.18 netmask 0xffffffff > inet 81.19.94.166 netmask 0xffffffff > inet 81.19.94.167 netmask 0xffffffff bird.conf: > # Override router ID > router id 81.19.68.227; > > #include filters.conf; > > filter ospf_metrics_for_lo0 { > # if source != RTS_DEVICE then reject; > > if net = 81.19.70.17/32 then { ospf_metric2 = 11; accept "70.17"; } else > if net = 81.19.70.18/32 then { ospf_metric2 = 19; accept "70.18"; } else > reject; > }; > > # Turn on global debugging of all protocols > debug protocols all; > > # This pseudo-protocol watches all interface up/down events. > protocol device { > scan time 10; # Scan interfaces every 10 seconds > }; > > protocol direct { > interface "lo0"; > } > > protocol kernel { > # export all; > scan time 15; > }; > > protocol ospf { > import all; > export filter ospf_metrics_for_lo0; > > area 70 { > nssa; > interface "bge0" { > hello 1; > dead 3; > }; > }; > }; But when I run bird, I've got: > bird -d > 29-09-2011 17:34:50 <TRACE> device1: Initializing > 29-09-2011 17:34:50 <TRACE> direct1: Initializing > 29-09-2011 17:34:50 <TRACE> kernel1: Initializing > 29-09-2011 17:34:50 <TRACE> ospf1: Initializing > 29-09-2011 17:34:50 <TRACE> device1: Starting > 29-09-2011 17:34:50 <TRACE> device1: Scanning interfaces > 29-09-2011 17:34:50 <TRACE> device1: State changed to feed > 29-09-2011 17:34:50 <TRACE> direct1: Starting > 29-09-2011 17:34:50 <TRACE> direct1: State changed to feed > 29-09-2011 17:34:50 <TRACE> kernel1: Starting > 29-09-2011 17:34:50 <TRACE> kernel1: State changed to feed > 29-09-2011 17:34:50 <TRACE> ospf1: Starting > 29-09-2011 17:34:50 <TRACE> ospf1: Adding area 0.0.0.70 > 29-09-2011 17:34:50 <TRACE> ospf1: State changed to feed > 29-09-2011 17:34:50 <INFO> Started > 29-09-2011 17:34:50 <TRACE> device1: State changed to up > 29-09-2011 17:34:50 <TRACE> direct1 < primary address 81.19.68.224/28 on interface bge0 added > 29-09-2011 17:34:50 <TRACE> direct1 < primary address 81.19.70.17/32 on interface lo0 added > 29-09-2011 17:34:50 <TRACE> direct1 > added [best] 81.19.70.17/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> direct1 < secondary address 127.0.0.0/8 on interface lo0 added > 29-09-2011 17:34:50 <TRACE> direct1 < secondary address 81.19.70.18/32 on interface lo0 added > 29-09-2011 17:34:50 <TRACE> direct1 > added [best] 81.19.70.18/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> direct1 < secondary address 81.19.94.166/32 on interface lo0 added > 29-09-2011 17:34:50 <TRACE> direct1 > added [best] 81.19.94.166/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> direct1 < secondary address 81.19.94.167/32 on interface lo0 added > 29-09-2011 17:34:50 <TRACE> direct1 > added [best] 81.19.94.167/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> direct1: State changed to up > 29-09-2011 17:34:50 <TRACE> kernel1: Connected to table master > 29-09-2011 17:34:50 <TRACE> kernel1 < rejected by protocol 81.19.70.18/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> kernel1 < rejected by protocol 81.19.70.17/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> kernel1 < rejected by protocol 81.19.94.166/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> kernel1 < rejected by protocol 81.19.94.167/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> kernel1: State changed to up > 29-09-2011 17:34:50 <TRACE> ospf1: Connected to table master > 29-09-2011 17:34:50 <TRACE> ospf1 < interface usbus0 created > 29-09-2011 17:34:50 <TRACE> ospf1 < interface usbus1 created > 29-09-2011 17:34:50 <TRACE> ospf1 < interface bge0 goes up > 29-09-2011 17:34:50 <TRACE> ospf1 < primary address 81.19.68.224/28 on interface bge0 added > 29-09-2011 17:34:50 <TRACE> ospf1: Adding interface bge0 (81.19.68.224/28) to area 0.0.0.70 > 29-09-2011 17:34:50 <TRACE> ospf1 < interface bge1 created > 29-09-2011 17:34:50 <TRACE> ospf1 < interface ipfw0 created > 29-09-2011 17:34:50 <TRACE> ospf1 < interface lo0 goes up > 29-09-2011 17:34:50 <TRACE> ospf1 < primary address 81.19.70.17/32 on interface lo0 added > 29-09-2011 17:34:50 <TRACE> ospf1 < secondary address 127.0.0.0/8 on interface lo0 added > 29-09-2011 17:34:50 <TRACE> ospf1 < secondary address 81.19.70.18/32 on interface lo0 added > 29-09-2011 17:34:50 <TRACE> ospf1 < secondary address 81.19.94.166/32 on interface lo0 added > 29-09-2011 17:34:50 <TRACE> ospf1 < secondary address 81.19.94.167/32 on interface lo0 added > 29-09-2011 17:34:50 <INFO> 70.18 > 29-09-2011 17:34:50 <TRACE> ospf1 < added 81.19.70.18/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> ospf1: Originating NSSA-LSA for 81.19.70.18/32 > 29-09-2011 17:34:50 <ERR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^ what is the ERR? > 29-09-2011 17:34:50 <INFO> 70.17 > 29-09-2011 17:34:50 <TRACE> ospf1 < added 81.19.70.17/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> ospf1: Originating NSSA-LSA for 81.19.70.17/32 > 29-09-2011 17:34:50 <ERR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^ what is the ERR? > 29-09-2011 17:34:50 <TRACE> ospf1 < filtered out 81.19.94.166/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> ospf1 < filtered out 81.19.94.167/32 dev lo0 > 29-09-2011 17:34:50 <TRACE> ospf1: State changed to up And so I don't see this routes. What am I doing wrong? > bird --version > BIRD version 1.3.3 > uname -a > FreeBSD xxxxx 8.2-20110713-SNAP FreeBSD 8.2-20110713-SNAP #0: Wed Jul 13 20:56:12 UTC 2011 root@nat-m1.rambler.ru:/usr/obj/usr/src/sys/DEVEL amd64 -- Fedor Dikarev Rambler Internet Holding

5 8

iBGP
by fredrik danerklint 30 Sep '11

30 Sep '11

Hi, FreeBSD 8.2 and Bird 1.3.3. I do my internal peering between routes on loopback interfaces. All the loopback interfaces is announced over ospf. To be able to get an bgp session the 'multi hop 4;' is needed. The question I have is what value should the 'next hop' be? I would like to have it to the neighbour address of the peering session but it seems it always the nearest physical network interface address (to the neighbour) that's 'next hop'. I did even try with setting bgp_next_hop=10.10.10.11; within the filter of the bgp protocol but that did not work. -- //fredan

2 7

Looking-Glass
by Mihai Claudiu Capatina 29 Sep '11

29 Sep '11

Hi, Does anybody know about an open-source looking-glass for BIRD ? Best Regards, Mihai Claudiu Capatina Managing Partner Vector Communications SRL Address : Aleea Cetatuia, Nr. 4, Bl. M22, Sc. 5, Et. 2, Ap. 276, Sect. 6, Bucuresti, 060834 Romania Phone: +40-729-087003 Fax: +40-318-146297 www.vector-communications.net

8 10

Directly connected interface redistribution problem
by Alex Bligh 29 Sep '11

29 Sep '11

I am using a config a little like the one below to import routes directed at interfaces into bird (by which I mean a /32 routed out of an interface with a static route) and then redistribute them into OSPF. The configuration in general works. If I a) start bird (assume an empty routing table) b) pause for several seconds / minutes c) add the interface d) add the /32 static route to the interface then all is well. If I omit step (b) above, then the route appears to get imported into the evrospf protocol (i.e. 'show protocols all evrospf' shows the same thing) but it never makes it to the OSPF peer (Quagga in this case). A "restart evrospf" fixes it. It /seems/ that if kernel routes are added whilst bird is starting up (or perhaps whilst the adjacency is being formed), then those changes are lost. Any ideas on this, or how to debug it further? I suppose I can work around it with a sleep(), but it is a bit arbitrary as I have no idea how long to sleep for. -- Alex Bligh # Import kernel routes. These come in with RTS_INHERIT protocol kernel evrkernel { persist; # Don't remove routes on bird shutdown scan time 10; # Scan kernel routing table every 20 seconds import all; export all; learn; # Learn all alien routes from the kernel } # This pseudo-protocol watches all interface up/down events. protocol device { scan time 10; # Scan interfaces every 10 seconds } # Import all directly connected routes. These come in with RTS_DEVICE protocol direct evrdirect { interface "-evrr-000000", "evrr-*"; export all; } protocol ospf evrospf { area 0.0.0.0 { interface "evrr-000000" { cost 20; priority 1; }; }; export filter { # RTS_INHERIT means routes from the kernel if net = 0.0.0.0/0 then reject; if (source = RTS_INHERIT) || (source = RTS_DEVICE) then { accept; } reject; }; }

2 1