- Bird-users - Mailing Lists

Protocols device and direct getting out of sync
by Tore Anderson 18 Feb '14

18 Feb '14

Hi, I've noticed that when adding addresses, BIRD will notice (i.e. "birdc show interface" will immediately show the newly-added address) but the direct protocol isn't notified until the periodic device scan triggers. The below console log with embedded comments shows what's happening. I'm running BIRD 1.4.0 and the config file contains simply: debug protocols all; protocol device {} protocol direct {} $ bird -d & [1] 22511 bird: device1: Initializing bird: direct1: Initializing bird: device1: Starting bird: device1: Scanning interfaces bird: device1: Connected to table master bird: device1: State changed to feed bird: Chosen router ID 87.238.42.150 according to interface em1 bird: direct1: Starting bird: direct1: Connected to table master bird: direct1: State changed to feed bird: Started bird: device1: State changed to up bird: direct1 < primary address 127.0.0.0/8 on interface lo added bird: direct1 < primary address 87.238.42.128/25 on interface em1 added bird: direct1 > added [best] 87.238.42.128/25 dev em1 bird: direct1 < primary address 100.66.7.5/32 on interface tun0 added bird: direct1 > added [best] 100.66.7.5/32 dev tun0 bird: direct1: State changed to up $ birdc show route; birdc show interface BIRD 1.4.0 ready. 100.66.7.5/32 dev tun0 [direct1 13:23:04] * (240) 87.238.42.128/25 dev em1 [direct1 13:23:04] * (240) BIRD 1.4.0 ready. lo up (index=1) MultiAccess AdminUp LinkUp Loopback Ignored MTU=65536 127.0.0.1/8 (Primary, scope host) em1 up (index=2) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 87.238.42.150/25 (Primary, scope univ) tun0 up (index=5) PtP Multicast AdminUp LinkUp MTU=1500 100.66.7.6/32 (Primary, opposite 100.66.7.5, scope univ) $ ip address add 192.0.2.1/32 dev lo bird: direct1 < primary address 192.0.2.1/32 on interface lo removed bird: direct1 < secondary address 127.0.0.0/8 on interface lo removed The debug messages from BIRD show up instantly. Not sure why why they say «removed», as 127.0.0.1 is unchanged, while 192.0.2.1 was *added*. $ birdc show route; birdc show interface BIRD 1.4.0 ready. 100.66.7.5/32 dev tun0 [direct1 13:23:04] * (240) 87.238.42.128/25 dev em1 [direct1 13:23:04] * (240) BIRD 1.4.0 ready. lo DOWN (index=1) MultiAccess AdminUp LinkUp Loopback Ignored MTU=65536 192.0.2.1/32 (Primary, scope univ) 127.0.0.1/8 (Unselected, scope host) em1 up (index=2) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 87.238.42.150/25 (Primary, scope univ) tun0 up (index=5) PtP Multicast AdminUp LinkUp MTU=1500 100.66.7.6/32 (Primary, opposite 100.66.7.5, scope univ) So here it has clearly noticed that there's an new address on lo, but for some reason it's not showing up in BIRD's routing table. Also, for some reason "lo" is now marked DOWN? bird: device1: Scanning interfaces bird: direct1 < primary address 192.0.2.1/32 on interface lo added bird: direct1 > added [best] 192.0.2.1/32 dev lo bird: direct1 < secondary address 127.0.0.0/8 on interface lo added $ birdc show route; birdc show interface BIRD 1.4.0 ready. 100.66.7.5/32 dev tun0 [direct1 13:23:05] * (240) 87.238.42.128/25 dev em1 [direct1 13:23:05] * (240) 192.0.2.1/32 dev lo [direct1 13:24:05] * (240) BIRD 1.4.0 ready. lo up (index=1) MultiAccess AdminUp LinkUp Loopback Ignored MTU=65536 192.0.2.1/32 (Primary, scope univ) 127.0.0.1/8 (Unselected, scope host) em1 up (index=2) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 87.238.42.150/25 (Primary, scope univ) tun0 up (index=5) PtP Multicast AdminUp LinkUp MTU=1500 So after the device scan, things look OK again. If I now proceed to add another address, it will instantly show up in the routing table, so this problem only appears to happen with the first address(es) I add (until the first time the device scan has been done after adding addresses), afterwards it seems to work fine. The impact of this behaviour is that it takes much longer than necessary for newly-added addresses to be advertised to the rest of the network (using RIP or OSPF or whatever). I can reduce the impact of the problem with using "protocol device { scan time 1; }" but it does seem a bit wasteful to poll the interfaces that often. Tore

2 2

ospf check link doesn't detect link up for vlan interfaces protocol
by Martin Kraus 17 Feb '14

17 Feb '14

Hi. I'm using a fairly standard setup on debian wheezy with bird 1.4.0 where ospf is connected to area 0 on the wan interface and I have a stub interface on a vlan interface to the local lan. interface "eth5.2001" { cost 10; stub yes; check link yes; } When I boot the router, bird doesn't detect that the vlan interface comes up and stays in the down state. I have to restart the ospf protocol so that bird rescans the interface and start propagating connected networks. During boot kernel logs that the link becomes ready ADDRCONF(NETDEV_CHANGE): eth5.2001: link becomes ready when I remove the "check link yes" parameter, it works correctly. Is this a bug or the problem is that vlan interfaces are not supported? thanks martin

1 0

Merge of bird and bird6
by Mathias Wolkert 13 Feb '14

13 Feb '14

Hello What is the status of the merging of bird and bird6? It is happening, right? /Tias

3 3

OSPF neighbor in PTMP network not removed on reloading configuration
by Cyrill Gössi 13 Feb '14

13 Feb '14

Hy BIRD community. I have a fairly simple setup of 3 routers connected in a "triangle-shape" through an ethernet network. The routers have IPs 15.0.0.1, 15.0.0.2 and 15.0.0.3. The essential part of the configuration files look as follows: // Router 15.0.0.1 protocol ospf { table baseTable; area 0.0.0.0 { interface "eth1" { type pointomultipoint; strict nonbroadcast yes; neighbors { 15.0.0.2; }; }; }; } // Router 15.0.0.2 protocol ospf { table baseTable; area 0.0.0.0 { interface "eth2" { type pointomultipoint; strict nonbroadcast yes; neighbors { 15.0.0.1; 15.0.0.3 }; }; }; } // Router 15.0.0.3 protocol ospf { table baseTable; area 0.0.0.0 { interface "eth3" { type pointomultipoint; strict nonbroadcast yes; neighbors { 15.0.0.2; }; }; }; } If I start the routers like this and sniff the traffic on "eth3" is see router 15.0.0.2 sending Hello-packets to both other routers. Routers 15.0.0.1 and 15.0.0.3 send their Hello-packets only to 15.0.0.2. So far so good! If I add the neighbor 15.0.0.1 to router 15.0.0.3 and also add neighbor 15.0.0.3 to router 15.0.0.1 and issue a "configure" to reload the configuration I see that all routers now issue 2 Hello packets - one for each of their neighbors listed in the neighbors {} section. Still - so far so good! However, if I now undo the last step (adding the neighbors to router 15.0.0.1 and 15.0.0.3) and issue the "configure" command again to let BIRD adopt to the new setting, all routers still keep on issuing exactly as before 2 Hello packets - one for each of their former neighbors. Why is that? How could I make BIRD aware that the neighbor-relationship has to be undone after having removed the neighbors from the list again? I'm sure I miss the obvious here. I will be glad about any help in this matter! Thanks in advance. Best, Cyrill

2 1

Compile error on ARM/Synology DS212+
by Michael 12 Feb '14

12 Feb '14

Hi, I am successfully using bird for OSPFv2 and OSPFv3 in a mixed network of FreeBSD, OpenBSD and Linux. Yesterday I wanted to add a Synology DS212+ to the network but it fails to compile. It seems to be some bison language issue. Maybe someone can help? Thanks in advance. Best regards, Michael DiskStation> make clean; ./configure --sysconfdir /etc --localstatedir /var/run --prefix=/usr/local --exec-prefix=/usr/local make -C obj clean make[1]: Entering directory `/usr/local/src/bird-1.4.0/obj' find . -name "*.[oa]" -o -name core -o -name depend -o -name "*.html" | xargs rm -f rm -f conf/cf-lex.c conf/cf-parse.* conf/commands.h conf/keywords.h rm -f ../bird ../birdcl ../birdc ../bird.ctl ../bird6.ctl .dep-stamp make[1]: Leaving directory `/usr/local/src/bird-1.4.0/obj' find . -name "*~" -or -name "*.[oa]" -or -name "\#*\#" -or -name TAGS -or -name core -or -name depend -or -name ".#*" | xargs rm -f 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... armv5tel-unknown-linux-gnueabi checking host system type... armv5tel-unknown-linux-gnueabi 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 whether POSIX threads are available... no checking whether CC supports -Wno-pointer-sign... yes checking whether CC supports -fno-strict-aliasing... yes checking whether CC supports -fno-strict-overflow... yes checking CFLAGS... -g -O2 -Wall -Wstrict-prototypes -Wno-parentheses -Wno-pointer-sign -fno-strict-aliasing -fno-strict-overflow checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... tools/install-sh -c checking for ranlib... ranlib checking for flex... flex checking for bison... bison checking for gm4... no checking for m4... m4 checking which OS configuration should we use... ./sysdep/cf/linux.h checking system-dependent directories... sysdep/linux sysdep/unix lib checking protocols... ok checking for linux/rtnetlink.h... yes checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking alloca.h usability... yes checking alloca.h presence... yes checking for alloca.h... yes checking whether 'struct sockaddr' has sa_len... no checking whether byte ordering is bigendian... no checking size of char... 1 checking size of short int... 2 checking size of int... 4 checking size of long int... 4 checking size of long long int... 8 checking for 8-bit type... char checking for 16-bit type... short int checking for 32-bit type... int checking for 64-bit type... long long int checking usual alignment of structures... 8 checking characteristics of time_t... 32-bit signed checking for struct ip_mreqn... yes checking for add_history in -lhistory... yes checking for tgetent in -lncurses... yes checking for rl_callback_read_char in -lreadline... yes checking for rl_crlf in -lreadline... yes checking for rl_ding in -lreadline... yes configure: creating ./config.status config.status: creating Makefile config.status: creating obj/Makefile config.status: creating obj/Rules config.status: creating obj/sysdep/autoconf.h config.status: obj/sysdep/autoconf.h is unchanged config.status: executing merge commands Merging system-dependent modules (sysdep/linux sysdep/unix lib) BIRD was configured with the following options: Source directory: . Object directory: obj Iproute2 directory: /etc/iproute2 System configuration: ./sysdep/cf/linux.h Debugging: no POSIX threads: no Routing protocols: bgp ospf pipe rip static Client: yes DiskStation> make make -C obj all make[1]: Entering directory `/usr/local/src/bird-1.4.0/obj' echo >sysdep/paths.h "/* Generated by Makefile, don't edit manually! */" echo >>sysdep/paths.h "#define PATH_CONFIG_FILE \"/etc/bird.conf\"" echo >>sysdep/paths.h "#define PATH_CONTROL_SOCKET \"/var/run/run/bird.ctl\"" if test -n "/etc/iproute2" ; then echo >>sysdep/paths.h "#define PATH_IPROUTE_DIR \"/etc/iproute2\"" ; fi make depend make[2]: Entering directory `/usr/local/src/bird-1.4.0/obj' mkdir -p nest filter proto/bgp proto/ospf proto/pipe proto/rip proto/static client doc touch .dir-stamp set -e ; for a in lib conf ; do make -C $a depend ; done make[3]: Entering directory `/usr/local/src/bird-1.4.0/obj/lib' gcc -I../ -I../.. -MM bitops.c checksum.c event.c io.c ip.c ipv4.c krt.c lists.c log.c main.c md5.c mempool.c netlink.c patmatch.c printf.c random.c resource.c slab.c slists.c xmalloc.c >depend make[3]: Leaving directory `/usr/local/src/bird-1.4.0/obj/lib' make[3]: Entering directory `/usr/local/src/bird-1.4.0/obj/conf' m4 -P ../../conf/gen_keywords.m4 ../../conf/confbase.Y ../../sysdep/unix/config.Y ../../sysdep/unix/krt.Y ../../sysdep/linux/netlink.Y ../../nest/config.Y ../../filter/config.Y ../../proto/bgp/config.Y ../../proto/ospf/config.Y ../../proto/pipe/config.Y ../../proto/rip/config.Y ../../proto/static/config.Y >keywords.h m4 -P ../../conf/gen_commands.m4 ../../client/cmds.m4 ../../conf/confbase.Y ../../sysdep/unix/config.Y ../../sysdep/unix/krt.Y ../../sysdep/linux/netlink.Y ../../nest/config.Y ../../filter/config.Y ../../proto/bgp/config.Y ../../proto/ospf/config.Y ../../proto/pipe/config.Y ../../proto/rip/config.Y ../../proto/static/config.Y | sort >commands.h m4 -P ../../conf/gen_parser.m4 ../../conf/confbase.Y ../../sysdep/unix/config.Y ../../sysdep/unix/krt.Y ../../sysdep/linux/netlink.Y ../../nest/config.Y ../../filter/config.Y ../../proto/bgp/config.Y ../../proto/ospf/config.Y ../../proto/pipe/config.Y ../../proto/rip/config.Y ../../proto/static/config.Y >cf-parse.y bison -bcf-parse -dv -pcf_ cf-parse.y cf-parse.y: warning: 1 nonterminal useless in grammar cf-parse.y: warning: 3 rules useless in grammar cf-parse.y:521.13-19: warning: nonterminal useless in grammar: expr_us cf-parse.y:692.4-39: warning: rule useless in grammar: expr_us: expr S cf-parse.y:693.4-36: warning: rule useless in grammar: expr_us: expr MS cf-parse.y:694.4-33: warning: rule useless in grammar: expr_us: expr US make[3]: *** [cf-parse.tab.c] Broken pipe make[3]: Leaving directory `/usr/local/src/bird-1.4.0/obj/conf' make[2]: *** [depend] Error 2 make[2]: Leaving directory `/usr/local/src/bird-1.4.0/obj' make[1]: *** [.dep-stamp] Error 2 make[1]: Leaving directory `/usr/local/src/bird-1.4.0/obj' make: *** [all] Error 2 DiskStation> cd obj/conf/ DiskStation> bison -bcf-parse -dv -pcf_ cf-parse.y cf-parse.y: warning: 1 nonterminal useless in grammar cf-parse.y: warning: 3 rules useless in grammar cf-parse.y:521.13-19: warning: nonterminal useless in grammar: expr_us cf-parse.y:692.4-39: warning: rule useless in grammar: expr_us: expr S cf-parse.y:693.4-36: warning: rule useless in grammar: expr_us: expr MS cf-parse.y:694.4-33: warning: rule useless in grammar: expr_us: expr US DiskStation> cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1985.74 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Synology 6282 board Revision : 0000 Serial : 0000000000000000 DiskStation> gcc -v Using built-in specs. Target: arm-none-linux-gnueabi Configured with: ../gcc-4.2/configure --build=i386-pc-linux-gnu --host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi --prefix=/opt --disable-nls --disable-static --with-as=/home/slug/optware/cs08q1armel/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-as --with-ld=/home/slug/optware/cs08q1armel/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-ld --enable-languages=c,c++ --disable-multilib --enable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libstdcxx-pch --enable-shared --enable-symvers=gnu --enable-__cxa_atexit Thread model: posix gcc version 4.2.3 DiskStation> bison -V bison (GNU Bison) 2.5.1 Written by Robert Corbett and Richard Stallman. Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. DiskStation> make -v GNU Make 3.82 Built for arm-none-linux-gnueabi Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

3 2

Source routing for static protocol
by Pierluigi Rolando 11 Feb '14

11 Feb '14

Hi everyone, At a first (and second) glance it's not possible to specify a source option for static routes, to achieve an effect similar to what happens under Linux with ip route add xxx.xxx.xxx/pp via yyy.yyy.yyy.yyy src zzz.zzz.zzz.zzz. Are there any plans to add this as a feature? Thanks, Pierluigi

2 1

[PATCH] Add the ability for a sysconfig file to determine extra parameters for bird
by Alex Bligh 06 Feb '14

06 Feb '14

On Ubuntu / Debian, you can use /etc/default/bird{,6} to specify parameters to be passed to the bird daemon. As far as I can tell, using the rpm spec file in the current srpm, you can't. I do NOT claim to be a Redhat expert, but a patch like this would seem to provide equivalent functionality. I am taking it /etc/sysconfig is the right place. Signed-off-by: Alex Bligh <alex(a)alex.org.uk> --- misc/bird.init | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/misc/bird.init b/misc/bird.init index 56842bf..7556dc5 100755 --- a/misc/bird.init +++ b/misc/bird.init @@ -22,6 +22,9 @@ BIRD4="yes" BIRD6="yes" +BIRD4ARGS= +BIRD6ARGS= + [ -f /etc/bird.conf ] || BIRD4="no" [ -f /usr/sbin/bird ] || BIRD4="no" [ "${NETWORKING}" = "yes" ] || BIRD4="no" @@ -30,6 +33,8 @@ BIRD6="yes" [ -f /usr/sbin/bird6 ] || BIRD6="no" [ "${NETWORKING_IPV6}" = "yes" ] || BIRD6="no" +[ -e /etc/sysconfig/bird ] && . /etc/sysconfig/bird + RETVAL=0 # See how we were called. @@ -38,7 +43,7 @@ case "$1" in if [ "$BIRD4" = "yes" ] then echo -n "Starting BIRD for IPv4: " - daemon bird + daemon bird ${BIRD4ARGS} RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/bird @@ -46,7 +51,7 @@ case "$1" in if [ "$BIRD6" = "yes" ] then echo -n "Starting BIRD for IPv6: " - daemon bird6 + daemon bird6 ${BIRD6ARGS} RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/bird6 -- 1.7.9.5

3 4

Bird IPv6 propagation route filtering
by arno.odermatt＠ch.schindler.com 05 Feb '14

05 Feb '14

All, I am running Bird6/rel.1.3.7 and using OSPF3 for IPv6. I need to setup IPv6 route propagation filtering but do not succeed. I got a bulk of IPv6 routes, but need to propgate to area 0.0.0.0 only the one, which comes in from tap0 (fed0:1701:f001::/64): show route fed0:1701:4::/64 dev lo [direct1 Jan16] * (240) fed0:1701:2::/64 dev GRE1-ETH6 [direct1 Jan16] * (240) dev GRE1-ETH6 [OIPv6 05:47] I (150/10) [172.16.128.111] fed0:1701:3::1/128 dev sit0 [direct1 Jan16] * (240) fed0:1701:a000::/64 via fe80::5efe:ac10:806f on GRE1-ETH6 [OIPv6 05:47] * E2 (150/10/10000) [172.16.128.111] fed0:1701:f004::/64 via fe80::5efe:ac10:8078 on GRE2-ETH6 [OIPv6 05:47] * E2 (150/10/10000) [172.16.128.120] fed0:1701:f002::/64 via fe80::5efe:ac10:806f on GRE1-ETH6 [OIPv6 05:47] * E2 (150/10/10000) [172.16.128.111] fed0:1701:f003::/64 via fe80::5efe:ac10:806f on GRE1-ETH6 [OIPv6 05:47] * E2 (150/10/10000) [172.16.128.111] fed0:1701:f001::/64 dev tap0 [direct1 Jan16] * (240) fed0:1701:f003:1102::/64 via fe80::5efe:ac10:806f on GRE1-ETH6 [OIPv6 05:47] * E2 (150/10/10000) [172.16.128.111] bird> Is this available at all? I am not managing to do this, I am missing something or doing something generally wrong? Pls. find relevant config details below: filter test_filter { if net ~[ fed0:1701:f001::/64 ] then accept; else reject; } protocol ospf OIPv6 { export filter test_filter; tick 2; # rfc1583compat yes; import all; area 0.0.0.0 { thank you very much for replying freundlich grüsst, kind regards, ****************************************************** Notice: The information contained in this message is intended only for use of the individual(s) named above and may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient of this message you are hereby notified that you must not use, disseminate , copy it in any form or take any action in reliance of it. If you have received this message in error please delete it and any copies of it and notify the sender immediately. *******************************************************

1 0

BIRD MPLS Route Reflector
by Tom Berryman 03 Feb '14

03 Feb '14

HI All, Is anyone out there using BIRD for an MPLS route reflector? I am looking for some advice / direction on the .conf for the VPNV4 table. Cheers, Tom

4 5

Include in configuration files
by Pierluigi Rolando 30 Jan '14

30 Jan '14

Hi everyone, Maybe it's common knowledge among power users, but today I found out about a very nifty feature of BIRD: the include directive can be used pretty much anywhere in a configuration file, including inside a protocol section. I don't know if this is intended or not as include is described as a global option in the documentation. If it's an official feature I think it's worth documenting. If not, I think it's worth making one :-) Thanks, Pierluigi

3 2