July 2011 - Bird-users - Mailing Lists

Feature requests
by Ondrej Zajicek 11 Jul '11

11 Jul '11

Hello We (BIRD developers) would like to know which major features you miss in BIRD and would like to be implemented. If you have some opinions on that issue, please write suggested features together with several sentences about why you think that is the feature we should implement or why you need that. This inquiry is oriented on long-term, major features, but if you have some minor requests, you are also welcome. Our current short-term plan is to fix RIP (and multipath for RIP) and implement Route Origin Authorization / RPKI drafts for BGP. Some examples: OSPF NSSA OSPF opaque LSAs .. or some other OSPF extensions BGP confederations BGP extended communities .. or some other BGP extensions MRT routing table dumps Some monitoring/statistics integration (SNMP, collectd ...) Route aggregation engine Static routes depedent on ping reachability BFD (Bidirectional Forwarding Detection) IS-IS Some ad-hoc wireless routing like OSPF MANET or OLSR Multicast routing? .. or perhaps no new big features, just some more work to already implemented areas? BTW, from these examples, my personal preference is currently on BFD. -- 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."

19 33

Open socket on OSPF Stub interfaces
by Neil Wilson 05 Jul '11

05 Jul '11

Hi, Is there a way of turning off the socket listen for OSPF interfaces marked as 'stub'? At the moment I'm running up against the 1024 open file limit on servers (such as VM hosts) with lots of interfaces. I could alter the ulimit but it seems a bit of a waste to have all those open sockets doing nothing. Could the code be altered to open the socket if the interface is reconfigured away from being a stub, or is there another reason for the listen being there on stub interfaces? Rgs Neil

4 10

as_path question
by Mikhail A. Grishin 05 Jul '11

05 Jul '11

Hi, Ordinary as_path from 'show route all' output usually looks like: ------------------------- 78.153.135.0/24 via 193.232.244.186 on bce1 [R48467x1 2011-07-04 16:16:21] (100) [AS44116i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 48467 44116 44116 BGP.next_hop: 193.232.244.186 BGP.local_pref: 100 ------------------------- Here is unusual as_path example: ------------------------- 94.228.160.0/20 via 193.232.244.186 on bce1 [R48467x1 2011-07-05 01:28:04] * (100) [i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 48467 { 49245 50448 } BGP.next_hop: 193.232.244.186 BGP.local_pref: 100 BGP.aggregator: 178.236.240.1 AS48467 What purpose of '{' and '}' at BGP.as_path output? Why at 'show route' we see only '[i]'? (expected to see the first AS in as_path)

4 5

Loopback not redistributed
by Pierre Rivenez 04 Jul '11

04 Jul '11

Hi, I have a problem using bird. I have two ospf instances running on a router. This router are connected to two routers. One instance for each link. On the two links I send two loopbacks with different ospf tag. But when a link fail and come back the ospf don't send again the loopback to the remote router. Do you know why ? Pierre

1 1

LSA Update checksum breaks with large LSA Updates
by Neil Wilson 04 Jul '11

04 Jul '11

Using Bird 1.3.1 OSPF with 'rx buffer large' in the config. This test system is a couple of bird instances talking to each other. I've noticed that when LSA updates get above 4000 the checksum system seems to break. Before: Jul 1 18:39:21 acer-aspire-5536 bird: cloudtest: Scheduling routing table calculation Jul 1 18:39:21 acer-aspire-5536 bird: cloudtest: LSUPD packet received from 192.168.0.201 via eth0 Jul 1 18:39:21 acer-aspire-5536 bird: cloudtest: length 3964 Jul 1 18:39:21 acer-aspire-5536 bird: cloudtest: router 192.168.0.201 Jul 1 18:39:21 acer-aspire-5536 bird: cloudtest: LSA Type: 0001, Id: 192.168.0.201, Rt: 192.168.0.201, Age: 0, Seq: 8000000a, Sum: 7113 Jul 1 18:39:21 acer-aspire-5536 bird: cloudtest: LSACK packet sent via eth0 Jul 1 18:39:21 acer-aspire-5536 bird: cloudtest: length 44 Jul 1 18:39:21 acer-aspire-5536 bird: cloudtest: router 192.168.0.20 Jul 1 18:39:21 acer-aspire-5536 bird: cloudtest: LSA Type: 0001, Id: 192.168.0.201, Rt: 192.168.0.201, Age: 0, Seq: 8000000a, Sum: 7113 After: Jul 1 18:39:26 acer-aspire-5536 bird: cloudtest: LSUPD packet received from 192.168.0.201 via eth0 Jul 1 18:39:26 acer-aspire-5536 bird: cloudtest: length 4192 Jul 1 18:39:26 acer-aspire-5536 bird: cloudtest: router 192.168.0.201 Jul 1 18:39:26 acer-aspire-5536 bird: cloudtest: LSA Type: 0001, Id: 192.168.0.201, Rt: 192.168.0.201, Age: 1, Seq: 8000000a, Sum: b77a Jul 1 18:39:26 acer-aspire-5536 bird: Received bad lsa checksum from 192.168.0.201: 7ab7 4f5b The two processes then get stuck in a loop constantly requesting, updating and failing. Any ideas where the issue might lie? Rgs Neil Wilson

2 2

Allowas-in in BIRD - possible to implement?
by Adrian Czapek 04 Jul '11

04 Jul '11

Hello, I am in dire need to accept my own AS in AS-PATH from my upstream provider. Is there any way to achieve it using bird? Regards -- Adrian Czapek

3 4

Hold timer expired: difference between Received/Error
by Arnold Nipper 01 Jul '11

01 Jul '11

Quick question: what's the difference between 2011-04-29 18:24:36 <RMT> XXXX: Received: Hold timer expired 2011-04-30 00:05:42 <RMT> YYYY: Error: Hold timer expired We are running BIRD 1.2.5 ready. TIA and best regards, Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold(a)nipper.de phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333

3 8