June 2014 - Bird-users - Mailing Lists

Behavior during OSPF premature aging
by Lennard Klein 25 Jun '14

25 Jun '14

Hi, When premature aging an LSA, bird seems to increase the LSA sequence number to its maximum (proto/ospf/lsupd.c line 616, in 1.4.3). RFC 2328 14.1 (page 156) states "An LSA can be flushed from the routing domain by setting its LS age to MaxAge, while leaving its LS sequence number alone, and then reflooding the LSA." While I don’t see a valid technical reason this should break, I seem to have a device in my network which ignores this updates LSA, I suspect it is doing an unsigned int comparison instead of a signed comparison. While I think the main fault lies with the other vendor, my question at this time is: what is the reasoning behind updating the sequence number to its maximum, even though the RFC says to leave it as-is? Regards, Lennard Klein This email is from Equinix (EMEA) B.V. or one of its associated companies in the territory from where this email has been sent. This email, and any files transmitted with it, contains information which is confidential, is solely for the use of the intended recipient and may be legally privileged. If you have received this email in error, please notify the sender and delete this email immediately. Equinix (EMEA) B.V.. Registered Office: Luttenbergweg 4, 1101 EC Amsterdam-Zuidoost, The Netherlands. Registered in The Netherlands No. 57577889.

2 1

bird 1.4.3 ospfv3 issue on openbsd
by Job Snijders 25 Jun '14

25 Jun '14

Hi all, I just upgraded from 1.4.0 to 1.4.3 (compiled from -current ports) on OpenBSD 5.5, now OSPFv3 adjecencies don't establish any longer, they remain stuck in exstart. I saw a thread a while ago about IPv6 issues on FreeBSD with 1.4.1, maybe this is related but the bug fix does not work on OpenBSD? syslog is filled with these messages: Jun 23 15:34:14 dcg-1 bird6: ospf1: Socket error on bnx0: Invalid argument Jun 23 15:34:24 dcg-1 last message repeated 6 times Jun 23 15:34:24 dcg-1 bird6: ospf1: Socket error on bnx2: Invalid argument Jun 23 15:34:24 dcg-1 bird6: ospf1: Socket error on bnx0: Invalid argument Jun 23 15:34:28 dcg-1 last message repeated 3 times this is my config: [root@dcg-1 ~]# cat /etc/bird6.conf log syslog all; router id 94.142.247.1; protocol kernel { scan time 20; export all; } protocol device { scan time 2; } protocol direct { interface "lo1"; interface "bnx0"; interface "bnx2"; } protocol static { route 2a02:898::/32 blackhole; } filter only_loopbacks { if net ~ [ 2a02:898:0:300:0:0:0:0/64{128,128} ] then accept; reject; } protocol ospf ospf1 { tick 2; rfc1583compat yes; import filter only_loopbacks; export filter only_loopbacks; area 0.0.0.0 { interface "bnx0", "bnx2" { hello 10; retransmit 2; wait 10; dead 40; type pointopoint; }; }; } [root@dcg-1 ~]# birdc6 show ospf nei BIRD 1.4.3 ready. ospf1: Router ID Pri State DTime Interface Router IP 195.85.225.5 128 exstart/ptp 00:34 bnx0 fe80::21f:12ff:fe1c:3482 Kind regards, Job

2 3

Re: Segmentation fault on EOR
by Ondrej Zajicek 21 Jun '14

21 Jun '14

On Sat, Jun 21, 2014 at 01:59:16AM +0400, Artyom Gavrichenkov wrote: > Hello Ondrej, > > 21.06.2014 01:15, Ondrej Zajicek ??????????: > >> In fact, this bug is not related to IPv6. It may appear even if bird > >> is used only for IPv4 routing, because multiprotocol extensions may be > >> also used in this case. > > > > Well, BIRD does not support IPv4 NLRI in multiprotocol extensions. > > This doesn't mean it may crash when the latter is sent to it, does it? No, regardless of this bug, they are just ignored as unknown route attributes. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago(a)crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."

1 0

Re: Segmentation fault on EOR
by Ondrej Zajicek 20 Jun '14

20 Jun '14

On Fri, Jun 20, 2014 at 08:32:29PM +0400, Evgeny Uskov wrote: > Hello, > > No, the bug I'm talking about was not fixed. It can be easily > reproduced on any of the versions 1.4.1, 1.4.2, 1.4.3 (by sending the > UPDATE message from my previous letter). You are right, i conflated two different bugs. This one is already fixed but only in git: https://gitlab.labs.nic.cz/labs/bird/commit/66370eac1f88ec74b3017f1c39038d7… > In fact, this bug is not related to IPv6. It may appear even if bird > is used only for IPv4 routing, because multiprotocol extensions may be > also used in this case. Well, BIRD does not support IPv4 NLRI in multiprotocol extensions. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago(a)crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."

1 0

Segmentation fault on EOR
by Evgeny Uskov 20 Jun '14

20 Jun '14

Hello, bird with version >= 1.4.1 has the following bug: it falls with segmentation fault when it receives certain BGP UPDATE messages. In particular, the problem is triggered by a message with attributes but without NLRI section. An example of such message is End-of-RIB marker (an empty UPDATE) with additional multiprotocol extension attributes (such as MP_UNREACH_NLRI): 0000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0010 00 1e 02 00 00 00 07 90 0f 00 03 00 01 01 The problem is caused by null pointer reference in the function bgp_set_next_hop: struct eattr *nh = ea_find(a->eattrs, EA_CODE(EAP_BGP, BA_NEXT_HOP)); ip_addr *nexthop = (ip_addr *) nh->u.ptr->data; If the case of the UPDATE message above, a->eattrs field is NULL, and hence nh is NULL too, resulting in SIGSEGV. In bird <= 1.4.0 this function is called in bgp_do_rx_update only when nlri_len != 0 (I'm not sure it's safe enough, but at least it doesn't cause this problem). However, in v1.4.1 this behavior has been changed, and now bgp_set_next_hop is called for every UPDATE message with positive attr_len + nlri_len.

2 1

about lo:0 interface
by 曾小小 20 Jun '14

20 Jun '14

hi My system is Ubuntu 13.04, kernel version is 3.8.0-21-generic, bird version is 1.3.10. I want to achieve lo: 0 (eg: 192.168.1.1/32) address as the route-id of the device, while learning through ospf routing protocol ip address to manage the device through this ip address. Configured as follows: 1: I'm on a device configured lo:0 interface address: ifconfig lo:0 192.168.1.1/32 root @ sr1 :/ usr / local / bird # ifconfig lo:0 lo: 0 Link encap: Local Loopback inet addr: 192.168.1.1 Mask: 0.0.0.0 UP LOOPBACK RUNNING MTU: 65536 Metric: 1 2: The bird in the configuration is as follows: In direct proto configured lo: 0 Interface protocol direct { interface "eth1", 192.168.1.1/32; } In the kernel configuration is as follows: protocol kernel { # Learn; # Learn all alien routes from the kernel # Persist; # Don't remove routes on bird shutdown device routes; scan time 15; # Scan kernel routing table every 15 seconds import none; # Default is import all export all; # Default is export none # Kernel table 5; # Kernel table to synchronize with (default: main) } The problem is found in bird default route pointing to the interface, and the interface address lo not found in the routing table, and why? bird> show interfaces 1001-lo up (index = 1) 1004 - MultiAccess AdminUp LinkUp Loopback Ignored MTU = 65536 1003 - 192.168.1.1 / 0 (Primary, scope univ) 127.0.0.1 / 8 (Unselected, scope host) root @ sr1 :/ usr / local / bird # birdc-v 0001 BIRD 1.3.10 ready. bird> show route 1007-0.0.0.0 / 0 dev lo [direct1 16:55] * (240) thanks.

2 1

route attribute scope
by Frederik Kriewitz 20 Jun '14

20 Jun '14

Hello, we noticed something which feels like an inconsistency/bug to us. So far we assumed that route attributes can be set in any filter of any protocol. But it seems like OSPF attributes can be set only in export filters of OSPF protocols. Here's an example configuration (Tested with BIRD 1.4.3): protocol static s_attr_test { import filter { bgp_community.add((65535,65281)); # working bgp_local_pref = 99; # working ospf_metric1=11; # not working ospf_metric2=12; # not working ospf_tag=123; # not working accept; }; route 10.50.0.0/30 via "lo"; } This is the result: # birdc show route all protocol s_attr_test BIRD 1.4.3 ready. 10.50.0.0/30 dev lo [s_attr_test 2014-06-20 12:35:25] * (200) Type: static-device unicast univ BGP.local_pref: 99 BGP.community: (65535,65281) As you can see the BGP attributes have been added correctly but the OSPF attributes are missing. Before we look further into this we would like to know if this is the intended behavior. Best Regards, Frederik Kriewitz

2 1

segfault error in bird6 after upgrading to 1.4.2
by Paul Emmons 18 Jun '14

18 Jun '14

Just upgraded to 1.4.2 from 1.3.9 and having issue with a ipv6 session that has 10k routes. Bird concierge as a route viewer ( no routing tables exchanged) Here is the error: Jun 17 17:21:30 collector kernel: [ 7107.186257] show_signal_msg: 3 callbacks suppressed Jun 17 17:21:30 collector kernel: [ 7107.186264] bird6[2295]: segfault at ffff800092721fa9 ip 00007fc03639dc2d sp 00007fff6d8ddfb0 error 5 in bird6[7fc036378000+70000] Jun 17 17:21:31 collector bird6: Started Jun 17 17:22:12 collector kernel: [ 7149.335707] bird6[15384]: segfault at ffff8000a4f155d9 ip 00007f0bdbc37c2d sp 00007fff5b0ea980 error 5 in bird6[7f0bdbc12000+70000] Jun 17 17:22:13 collector bird6: Started Jun 17 17:23:33 collector kernel: [ 7229.888236] bird6[15638]: segfault at ffff8000d3104cc9 ip 00007fbf1e824c2d sp 00007fff2cefb290 error 5 in bird6[7fbf1e7ff000+70000] Jun 17 17:23:33 collector bird6: Started Jun 17 17:24:00 collector kernel: [ 7256.689590] bird6[15710]: segfault at ffff8000c005edf9 ip 00007f69599a1c2d sp 00007fff3ffa1160 error 5 in bird6[7f695997c000+70000] Jun 17 17:24:00 collector bird6: Started Jun 17 17:25:43 collector kernel: [ 7360.327092] bird6[15741]: segfault at ffff8000a909a329 ip 00007f4195995c2d sp 00007fff56f65c30 error 5 in bird6[7f4195970000+70000] Jun 17 17:25:44 collector bird6: Started Jun 17 17:26:29 collector bird6: Reconfiguring Jun 17 17:26:29 collector bird6: Removing protocol Hurricane Stays up after I comment out users: #protocol bgp Hurricane { # description "as6939"; # local as 65000; # neighbor 2001:504:3b::14 as 6939; # route limit 35000; #} I've tried it with and without the route limit in it. There are <10k routes being sent. If I try to send that many routes (actually a full table) from another peer I do get the same error. It seems to be an issue with going over a certain number of ipv6 routes Thanks - Paul

2 1

check_mk bird plugin
by Frederik Kriewitz 18 Jun '14

18 Jun '14

Hello, our bird plugin for the check_mk monitoring system just made it to version 1.0. It's available here: https://github.com/freddy36/check_mk_extensions/tree/master/bird I tried to add it to the Related Software page of the wiki, but it seems like I can't do that. Best Regards, Freddy

2 1

Default route not picked up by OSPF?
by Grzegorz Nosek 16 Jun '14

16 Jun '14

Hi, I'm using bird to autoconfigure networking between a bunch of VMs running on a bunch of hosts. It basically looks like: - OSPF on every host (connecting host<->VMs) - OpenVPN in tap mode across all hosts - BGP running over that VPN The net result is that I have all VM private addresses propagated everywhere. It generally works fine except during host startup, where I regularly end up with VMs lacking the default route (which should have been supplied via OSPF). `birdc reload my_ospf` from the host makes the routes appear on the VMs, so I believe bird is configured correctly (i.e. it's only a transient issue, the routes aren't filtered out). The hosts have static default routes. OS is Ubuntu 12.04, using bird from the PPA (1.4.x). Is this a known issue (e.g. with daemon start order or whatever)? Any hints? I wish I had more diagnostics but like I said, it happens early in the boot process. Best regards, Grzegorz Nosek

1 0