Hi! New version is ready. Santiago made a great job in bugfixing my very old code. And he added OSPFv3. :-) Version 1.2.0 (2010-01-05) o Implements OSPFv3 (IPv6 support for OSPF). Because the code is shared with OSPFv2 and there were deep changes in it, we suggest caution during upgrade to OSPF users. Some advanced features (like NSSA, vlinks and authentication) are not yet implemented. o Implements MRTdump - binary logging protocol compatible with other routing daemons. Only BGP part of MRTdump is yet implemented. o Changes default value of BGP attribute LOCAL_PREF from 0 to 100. Use 'default bgp_local_pref 0' BGP protocol option for the old behavior. The new value is suggested by RFC 4277. o Changes default mode of pipes from opaque to transparent. Use 'mode opaque' protocol option if the old behavior is needed. Opaque pipe mode is deprecated and might be removed in the future. All distro packages will follow soon. Ondrej
On Thu, Jan 14, 2010 at 11:19:03AM +0100, Ondrej Filip wrote:
Hi! New version is ready. Santiago made a great job in bugfixing my very old code. And he added OSPFv3. :-)
Version 1.2.0 (2010-01-05) o Implements OSPFv3 (IPv6 support for OSPF). Because the code is shared with OSPFv2 and there were deep changes in it, we suggest caution during upgrade to OSPF users. Some advanced features (like NSSA, vlinks and authentication) are not yet implemented.
I would add two more notes to OSPFv3: 1) There is a bug in OSPFv3 implementation in current Quagga that makes problems together with BIRD slightly different behavior. So currently i would suggest not to mix BIRD and Quagga routers in OSPFv3. It will be probably fixed in new Quagga release. Sees this for details: http://lists.quagga.net/pipermail/quagga-dev/2009-December/007480.html http://lists.quagga.net/pipermail/quagga-dev/2009-December/007571.html As Quagga uses a different code for OSPFv2 (IPv4) and OSPFv3 (IPv6), OSPFv2 users are not affected and in works OK. 2) OSPFv3 was not tested on *BSD systems. OSPFv2 should work on *BSD, but generally i would suggest to keep version 1.1.7 for OSFP *BSD users. We will address this in the next version. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@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."
On 14/01/2010 10:19, Ondrej Filip wrote: [Upon announcing 1.2.0]
o Implements MRTdump - binary logging protocol compatible with other routing daemons. Only BGP part of MRTdump is yet implemented.
Is any body using this yet ? I am looking to store and archive BGP RIB changes on some customer networks in order to help with future trouble shooting. BIRD has been so rock solid in other regards that I expect the MRT support will be very good. I just can't find any docs yet ;-) Andy -- // www.netsumo.com // Professional network engineering consultancy // // uk ddi: +44(0)20 7993 1702 // us ddi: (415) 520 3589 //
On Sat, Feb 20, 2010 at 12:47:47PM +0000, Andy Davidson wrote:
On 14/01/2010 10:19, Ondrej Filip wrote: [Upon announcing 1.2.0]
o Implements MRTdump - binary logging protocol compatible with other routing daemons. Only BGP part of MRTdump is yet implemented.
Is any body using this yet ?
I am looking to store and archive BGP RIB changes on some customer networks in order to help with future trouble shooting. BIRD has been so rock solid in other regards that I expect the MRT support will be very good. I just can't find any docs yet ;-)
Currently, BIRD supports only storing BGP messages/updates in MRTdump format, the RIP/routing table dump is not implemented. It is documented in User's guide, option 'mrtdump' in sections 3.2 and 3.3. http://bird.network.cz/?get_doc&f=bird-3.html#ss3.2 -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@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."
participants (3)
-
Andy Davidson -
Ondrej Filip -
Ondrej Zajicek