- Bird-users - Mailing Lists

build: Fix building without BGP protocol
by Sergey Popovich 26 Sep '13

26 Sep '13

Hello, BIRD developers! Currently BIRD fails to build without BGP protocol, due to missing keyword definitions in parser sources *.Y Simple patch, addressing this issue attached. -- SP5474-RIPE Sergey Popovich

2 1

Re: OSPF segfault
by 1 Игорь 25 Sep '13

25 Sep '13

> Could you also send me the binary? http://yadi.sk/d/P8wCizig9rsys Its compiled from sources taken from here: ftp://bird.network.cz/pub/bird/bird-1.3.11.tar.gz core file generated from it. But the same segfaults is for Debian 7u1 repository ( version 1.3.7) and .deb from bird.network.cz. > Well, there is no simple way to do it. You can use 'stubnet' option > with hidden and/or summary attribute to eliminate these, like: > > stubnet 10.16.a.254/32 { hidden; }; > > or > > stubnet 10.16.a.128/25 { summary; hidden; }; > The problem that the amount of /32 prefixes is too large (about 250 /32 addresses - one for each VLAN), and wrote stubnet option for each /32 is madness (.

1 0

Fwd: OSPF segfault
by 1 Игорь 24 Sep '13

24 Sep '13

> I guess that OSPF iface option 'rx buffer large' should also fix this. > Could you try it? But definitely, it shouldn't crash even without this. Thank you. Of course it's helps. The only thing i could do is http://bit.ly/1alMqek Just one question: do i need to add this option on interfaces to core? Now i have no problem with them. > Could you get core dump of crashed BIRD for me? (i.e. run BIRD with > ulimit -c unlimited get it crashed.) core : http://yadi.sk/d/eRv1MON09qKHx In gdb i have seen http://pastebin.com/kqsAM01L What about /32 secondaries? Can I avoid OSPF from learning them.

1 0

Re: OSPF segfault
by 1 Игорь 24 Sep '13

24 Sep '13

MTU is standart 1500. I'm just realized that i forgot to explain network topology, so, if it helps: I have two routers R1C1 and R2C1 with interfaces bond0 (eth0 + eth1). On both routers i setting up many VLAN (about 250) - for example bond0.001-bond0.250 with addresses 10.16.a.1/24 and 10.16.a.2/24. Over this VLAN works VRRP (keepalived) with VIP 10.16.a.254. For one half of interfaces default router (VRRP address owner) is R1C1 and for another half R2C1 This interfaces I add to Area 1 and make them stub. Between this routers I have two VLAN: 4012 and 4021 also in Area 1 for interconnection of this routers. On every router i have VLAN for connecting them to Core router in Area0 (Vlan 4001 for R1C1 and 4002 for R2C1). Core announce to R1C1 and R2C1 default route and 10.0.0.0/8. Also i have Router ID addresses on lo - 10.0.1.1/32 and 10.0.1.2/32 in Area 0. If I setup clients vlan (bond0.001-bond0.250) only on one of the routers (R1C1 or R2C1, no matter on what, for example R2C1, like in pastebin), and enable second, segfault occurs right after state FULL on first router who try to announce prefixes to his neighbour R1C1, who have no clients interfaces up. Core router in Area0 always receive routes without any trouble. I discovered three ways to avoid segfault, and make things works: 1) disable interfaces 4012 and 4021 which interconnects routers R1C1 and R2C1. In that case another router receive routes from core, which receive it from first, so traffic betwen routers will go through Core router, not wery good. 2) set interfaces 4012 and 4021 in Area 0, I think its wrong topology. 3) set MTU on interfaces 4012 and 4021 to 9000. From debug i discovered that LS Update massage have size about 6500. I hope that helps. Another question a wanted to ask - I found that in routing table appears routes to VRRP IP (10.16.a.254), so, in result, i have in routing table route to network 10.16.a.0/24 and route to host in this network 10.16.a.254. Is it possible to avoid OSPF to learn secondary addresses /32 from interface?

2 1

New bird functionality
by Thierry FOURNIER 24 Sep '13

24 Sep '13

Hello, I submit two patched. 0001-PATCH-FLX-Add-command-line-option-for-specifying-the.patch The first one is to add the -P <pidfile> argument on the command line. On some distributions, the pidfile is managed into the start script and not into the configuration file. 0003-FEAT-Add-protocol-volatile.patch The second patch is new protocol. I named it "protocol volatile". This permit to add routes into bird via the control socket. These route are volatile: when bird restart, they are lost. This is useful for servers using transparent redirect and transparent binding like "squid" or "haproxy". This two softs can receive trafic for an ip not present on the system. This new feature "protocol volatile" permit to do high avalaibility infrastructure with announcing these routes only if the service is avalaible. This permit also to do load-balacing: if many computers annouce the same route, the router can be use ecmp algorithm for the repartion. Thierry FOURNIER

2 1

Re: OSPF segfault
by 1 Игорь 24 Sep '13

24 Sep '13

Another thing, that i have discovered, is that every works normal if i set mtu 9000 on all interfaces between routers in area. If config is needed, i attach it: # Configure logging #log syslog { debug, trace, info, remote, warning, error, auth, fatal, bug }; log stderr all; log "/var/log/bird.log" all; filter OSPF_in { if ( net=0.0.0.0/0 || net ~ 10.0.0.0/8 ) then accept; else reject; }; filter OSPF_out { if (net ~ 10.16.0.0/12 ) then accept; else reject; }; # This pseudo-protocol performs synchronization between BIRD's routing # tables and the kernel. If your kernel supports multiple routing tables # (as Linux 2.2.x does), you can run multiple instances of the kernel # protocol and synchronize different kernel tables with different BIRD tables. protocol kernel { learn; # Learn all alien routes from the kernel debug {states,routes,filters,interfaces}; 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 # kernel table 5; # Kernel table to synchronize with (default: main) } # This pseudo-protocol watches all interface up/down events. protocol device { scan time 10; # Scan interfaces every 10 seconds } protocol ospf C1{ rfc1583compat yes; router id 10.0.1.1; # ecmp; import filter OSPF_in; # export filter OSPF_out; export none; debug {states,routes,filters,interfaces}; # debug all; area 0{ stub no; interface "bond0.4001"{ type bcast; cost 100; hello 1; dead count 3; retransmit 6; transmit delay 5; wait 30; authentication cryptographic; password "xxx"; }; interface 10.0.1.1/32 { stub 1; }; }; area 1{ stub yes; interface "bond0.4012", "bond0.4021"{ type bcast; cost 10; hello 1; dead count 3; retransmit 6; transmit delay 5; wait 30; }; interface 10.16.0.0/12 { stub 1; cost 10; }; }; }

2 1

Fwd: OSPF segfault
by 1 Игорь 24 Sep '13

24 Sep '13

I'm sorry, i didn't send first message: Hello, i have some problem with bird, when it starts and change state to FULL with neighbour in same area, i have a segfault: http://pastebin.com/9AMJYyTJ What more information I need to provide?

1 0

BSD & non-/32 prefixes on p2p linkes
by Alexander V. Chernikov 21 Sep '13

21 Sep '13

Hello list! Currently bird assumes (bsd sysdep) that any prefix on p2p link is /32. For example: bird: direct1 < primary address 10.0.0.3/31 on interface gif15 added bird: Ignoring bogus prefix 10.0.0.3/31 received via direct1 bird: direct1 > invalid 10.0.0.3/31 dev gif15 IPv6 case was fixed in 3f5843740 <https://gitlab.labs.nic.cz/labs/bird/commit/3f58437405f8e37e9c14d83274a6b82…>. Can we do the same for IPv4 ?

2 4

bird + RIP = crash
by Eugene M. Zheganin 21 Sep '13

21 Sep '13

Hi. I'm trying to get rid of quagga on most of my routers. When they run BGP/OSPF everything is fine, but when it comes to RIP, bird crashes. I run bird on a set of VPN tunnels, mostly gre. I need RIP because Cisco marketoids keep on manufacturing small boxes that cannot run OSPF, only RIP is available. Bird crashes as soon as the protocol exchange is started. Here's a backtrace along with some info about the setup: ===Cut=== [emz@moscow-alpha:~/bird.cores]# gdb /usr/local/sbin/bird bird.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `bird'. Program terminated with signal 6, Aborted. Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00000008007a3abc in kill () from /lib/libc.so.7 (gdb) bt full #0 0x00000008007a3abc in kill () from /lib/libc.so.7 No symbol table info available. #1 0x00000008007a28bb in abort () from /lib/libc.so.7 No symbol table info available. #2 0x000000000044ef49 in bug (msg=Could not find the frame base for "bug". ) at log.c:254 args = Could not find the frame base for "bug". (gdb) bt #0 0x00000008007a3abc in kill () from /lib/libc.so.7 #1 0x00000008007a28bb in abort () from /lib/libc.so.7 #2 0x000000000044ef49 in bug (msg=Could not find the frame base for "bug". ) at log.c:254 #3 0x0000000000437aa6 in advertise_entry (p=0x800a1f920, b=0x800a5b004, whotoldme=2886730539, iface=0x0) at ../../../proto/rip/rip.c:330 #4 0x0000000000437d07 in process_block (p=0x800a1f920, block=0x800a5b004, whotoldme=2886730539, iface=0x0) at ../../../proto/rip/rip.c:386 #5 0x0000000000438054 in rip_process_packet (p=0x800a1f920, packet=0x800a5b000, num=1, whotoldme=2886730539, port=520, iface=0x0) at ../../../proto/rip/rip.c:449 #6 0x0000000000438349 in rip_rx (s=0x800a0e400, size=20) at ../../../proto/rip/rip.c:504 #7 0x00000000004497ef in sk_read (s=0x800a0e400) at io.c:1493 #8 0x0000000000449fe4 in io_loop () at io.c:1707 #9 0x00000000004504fd in main (argc=3, argv=0x7fffffffed48) at main.c:745 (gdb) ===Cut=== ===Cut=== [emz@moscow-alpha:~/bird.cores]# uname -a FreeBSD moscow-alpha 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #1: Thu Mar 29 16:14:11 MSK 2012 emz@moscow-alpha:/usr/obj/usr/src/sys/MOSCOW amd64 ===Cut=== ===Cut=== /* would be nice to have named lists for these ! :) */ filter importripv4 { if net ~ [ 94.159.37.112/29, 192.168.21.0/24, 172.16.0.95/32, 172.16.3.4/32, 172.16.3.26/32, 172.16.3.28/32, 172.16.3.32/32, 172.16.3.36/32, 172.16.3.42/32, 172.16.3.48/32, 172.16.3.50/32, 172.16.3.66/32, 172.16.3.68/32, 172.16.3.106/32, 172.16.3.108/32, 172.16.3.116/32, 172.16.3.132/32, 172.16.3.136/32, 172.16.3.142/32, 172.16.3.144/32, 172.16.3.146/32, 172.16.3.154/32, 172.16.3.174/32, 172.16.3.184/32, 172.16.3.188/32, 172.16.3.252/32, 172.16.5.0/32, 172.16.5.2/32, 172.16.5.4/32, 172.16.5.8/32, 172.16.0.94/32, 172.16.3.5/32, 172.16.3.27/32, 172.16.3.29/32, 172.16.3.33/32, 172.16.3.37/32, 172.16.3.43/32, 172.16.3.49/32, 172.16.3.51/32, 172.16.3.67/32, 172.16.3.69/32, 172.16.3.107/32, 172.16.3.109/32, 172.16.3.117/32, 172.16.3.133/32, 172.16.3.137/32, 172.16.3.143/32, 172.16.3.145/32, 172.16.3.147/32, 172.16.3.155/32, 172.16.3.175/32, 172.16.3.185/32, 172.16.3.189/32, 172.16.3.253/32, 172.16.5.1/32, 172.16.5.3/32, 172.16.5.5/32, 172.16.5.9/32 ] then reject; accept; } filter exportripv4 { if source = RTS_BGP then reject; if net ~ [ 94.159.37.112/29 ] then reject; accept; } protocol rip ripv4 { interface "gre21", "gre25", "gre6"; honor neighbor; import filter importripv4; export filter exportripv4; } ===Cut=== ===Cut=== [emz@moscow-alpha:/]# ifconfig gre21 gre21: flags=b051<UP,POINTOPOINT,RUNNING,LINK0,LINK1,MULTICAST> metric 0 mtu 1476 tunnel inet 94.159.37.114 --> 188.133.159.62 inet 172.16.3.184 --> 172.16.3.185 netmask 0xffffffff [emz@moscow-alpha:/]# ifconfig gre25 gre25: flags=b051<UP,POINTOPOINT,RUNNING,LINK0,LINK1,MULTICAST> metric 0 mtu 1476 tunnel inet 94.159.37.114 --> 178.219.36.237 inet 172.16.5.2 --> 172.16.5.3 netmask 0xffffffff [emz@moscow-alpha:/]# ifconfig gre6 gre6: flags=b051<UP,POINTOPOINT,RUNNING,LINK0,LINK1,MULTICAST> metric 0 mtu 1476 tunnel inet 94.159.37.114 --> 213.33.223.158 inet 172.16.3.42 --> 172.16.3.43 netmask 0xffffffff ===Cut=== Thanks. Eugene.

2 3

Re: OSPF: LSA disappeared
by Bao Nguyen 21 Sep '13

21 Sep '13

Just want to add to this thread that I'm seeing this behavior on BIRD as well, I'm seeing this on all the machines that I've installed. From the timer, it appeared to happened every 5 seconds.... root@sje17:~# birdc -v 0001 BIRD 1.3.4 ready. Jan 8 02:34:30 sje17 bird: OSPF: LSA disappeared (Type: 0005, Id: 10.25.206.123, Rt: 10.25.15.11) Jan 8 02:34:30 sje17 bird: OSPF: LSA disappeared (Type: 0005, Id: 10.25.205.147, Rt: 10.25.15.17) Jan 8 02:34:30 sje17 bird: OSPF: LSA disappeared (Type: 0001, Id: 10.25.15.3, Rt: 10.25.15.3) Jan 8 02:34:30 sje17 bird: OSPF: LSA disappeared (Type: 0001, Id: 10.25.15.4, Rt: 10.25.15.4) Jan 8 02:34:30 sje17 bird: OSPF: LSA disappeared (Type: 0002, Id: 10.25.202.1, Rt: 10.25.239.11) Jan 8 02:34:30 sje17 bird: OSPF: LSA disappeared (Type: 0002, Id: 10.25.201.1, Rt: 10.25.239.10) Jan 8 02:34:30 sje17 bird: OSPF: LSA disappeared (Type: 0002, Id: 10.25.201.13, Rt: 10.25.239.10) Jan 8 02:34:30 sje17 bird: OSPF: LSA disappeared (Type: 0005, Id: 10.25.201.12, Rt: 10.25.10.4) Jan 8 02:34:35 sje17 bird: OSPF: LSA disappeared (Type: 0005, Id: 10.25.206.123, Rt: 10.25.15.11) Jan 8 02:34:35 sje17 bird: OSPF: LSA disappeared (Type: 0005, Id: 10.25.205.147, Rt: 10.25.15.17) Jan 8 02:34:35 sje17 bird: OSPF: LSA disappeared (Type: 0001, Id: 10.25.15.3, Rt: 10.25.15.3) Jan 8 02:34:35 sje17 bird: OSPF: LSA disappeared (Type: 0001, Id: 10.25.15.4, Rt: 10.25.15.4) Jan 8 02:34:35 sje17 bird: OSPF: LSA disappeared (Type: 0002, Id: 10.25.202.1, Rt: 10.25.239.11) Jan 8 02:34:35 sje17 bird: OSPF: LSA disappeared (Type: 0002, Id: 10.25.201.1, Rt: 10.25.239.10) Jan 8 02:34:35 sje17 bird: OSPF: LSA disappeared (Type: 0002, Id: 10.25.201.13, Rt: 10.25.239.10) Jan 8 02:34:35 sje17 bird: OSPF: LSA disappeared (Type: 0005, Id: 10.25.201.12, Rt: 10.25.10.4) -bn 0216331C

3 7