Revision 0c75411b

View differences:

NEWS
1
Version 1.2.0 (2010-01-05)
2
  o Implements OSPFv3 (IPv6 support for OSPF). Because the code is
3
    shared with OSPFv2 and there were deep changes in it, we suggest
4
    caution during upgrade to OSPF users. Some advanced features
5
    (like NSSA, vlinks and authentication) are not yet implemented.
6
  o Implements MRTdump - binary logging protocol compatible with other
7
    routing daemons. Only BGP part of MRTdump is yet implemented.
8
  o Changes default value of BGP attribute LOCAL_PREF from 0 to 100.
9
    Use 'default bgp_local_pref 0' BGP protocol option for the old
10
    behavior. The new value is suggested by RFC 4277.
11
  o Changes default mode of pipes from opaque to transparent.
12
    Use 'mode opaque' protocol option if the old behavior is needed.
13
    Opaque pipe mode is deprecated and might be removed in the future.
14

  
1 15
Version 1.1.7 (2009-12-20)
2 16
  o Implements BGP Route Refresh (RFC 2918).
3 17
  o Implements route reload command.
README
63 63
	o  Multiple routing tables
64 64
	o  BGP
65 65
	o  RIP
66
	o  OSPF (IPv4 only)
66
	o  OSPF
67 67
	o  Static routes
68 68
	o  Inter-table protocol
69 69
	o  Command-line interface (using the `birdc' client; to get
......
77 77

  
78 78
What is missing:
79 79

  
80
	o  OSPF for IPv6
81 80
	o  See the TODO list
82 81

  
83 82
Good Luck and enjoy the BIRD :)
TODO
49 49
	- RFC2370 opaque LSA's
50 50
	- Limit export rate of external LSAs (like Gated does)
51 51
	- Bugfix in link state retransmission list (aging)
52
	- Rewrite the "dirty patch" in OSPF database (LSA_T_NET)
53 52
	- Graceful OSPF restart - RFC3623
doc/bird.sgml
78 78
	<item>multiple routing tables
79 79
	<item>the Border Gateway Protocol (BGPv4)
80 80
	<item>the Routing Information Protocol (RIPv2)
81
	<item>the Open Shortest Path First protocol (OSPFv2)
81
	<item>the Open Shortest Path First protocol (OSPFv2, OSPFv3)
82 82
	<item>a virtual protocol for exchange of routes between different routing tables on a single host
83 83
	<item>a command-line interface allowing on-line control and inspection
84 84
		of status of the daemon
......
347 347
	Specifies a set of interfaces on which the protocol is activated with
348 348
	given interface-specific options. A set of interfaces specified by one
349 349
	interface option is described using an interface pattern. The
350
	interface pattern consists of a sequence of clauses (separted by
350
	interface pattern consists of a sequence of clauses (separated by
351 351
	commas), each clause may contain a mask, a prefix, or both of them. An
352 352
	interface matches the clause if its name matches the mask (if
353 353
	specified) and its address matches the prefix (if specified). Mask is
......
508 508
	Reload configuration from a given file. BIRD will smoothly
509 509
	switch itself to the new configuration, protocols are
510 510
	reconfigured if possible, restarted otherwise. Changes in
511
	filters usualy lead to restart of affected protocols. If
511
	filters usually lead to restart of affected protocols. If
512 512
	<cf/soft/ option is used, changes in filters does not cause
513 513
	BIRD to restart affected protocols, therefore already accepted
514 514
	routes (according to old filters) would be still propagated,
......
991 991
	received from its neighbor against the new filter. As these
992 992
	routes might not be available, there is a BGP protocol
993 993
	extension Route Refresh (specified in RFC 2918) that allows
994
	BGP speaker to request re-advertisment of all routes from its
994
	BGP speaker to request re-advertisement of all routes from its
995 995
	neighbor. This option specifies whether BIRD advertises this
996 996
	capability and accepts such requests. Even when disabled, BIRD
997 997
	can send route refresh requests. Default: on.
......
1301 1301
<sect1>Introduction
1302 1302

  
1303 1303
<p>Open Shortest Path First (OSPF) is a quite complex interior gateway
1304
protocol. The current IPv4 version (OSPFv2) is defined
1305
in RFC 2328<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc2328.txt">. It's a link
1306
state (a.k.a. shortest path first) protocol -- each router maintains a database
1307
describing the autonomous system's topology. Each participating router
1308
has an identical copy of the database and all routers run the same algorithm
1309
calculating a shortest path tree with themselves as a root.
1310
OSPF chooses the least cost path as the best path.
1311
(OSPFv3 - OSPF for IPv6 is not supported yet.)
1304
protocol. The current IPv4 version (OSPFv2) is defined in RFC
1305
2328<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc2328.txt"> and
1306
the current IPv6 version (OSPFv3) is defined in RFC 5340<htmlurl
1307
url="ftp://ftp.rfc-editor.org/in-notes/rfc5340.txt">  It's a link state
1308
(a.k.a. shortest path first) protocol -- each router maintains a
1309
database describing the autonomous system's topology. Each participating
1310
router has an identical copy of the database and all routers run the
1311
same algorithm calculating a shortest path tree with themselves as a
1312
root. OSPF chooses the least cost path as the best path.
1312 1313

  
1313 1314
<p>In OSPF, the autonomous system can be split to several areas in order
1314 1315
to reduce the amount of resources consumed for exchanging the routing
......
1421 1422
	 at periodical intervals of <m/num/ seconds. The default value is 1.
1422 1423

  
1423 1424
	<tag>networks { <m/set/ }</tag>
1424
         Definition of area IP ranges. This is used in summary lsa origination.
1425
         Definition of area IP ranges. This is used in summary LSA origination.
1425 1426
	 Hidden networks are not propagated into other areas.
1426 1427

  
1427 1428
	<tag>stubnet <m/prefix/ { <m/options/ }</tag>
......
1525 1526
	<tag>authentication cryptographic</tag>
1526 1527
	 16-byte long MD5 digest is appended to every packet. For the digest
1527 1528
         generation 16-byte long passwords are used. Those passwords are 
1528
         not sent via network, so this mechanismus is quite secure.
1529
         not sent via network, so this mechanism is quite secure.
1529 1530
         Packets can still be read by an attacker.
1530 1531

  
1531 1532
	<tag>password "<M>text</M>"</tag>
......
1754 1755

  
1755 1756
<p>RIP is a very simple protocol, and it has a lot of shortcomings. Slow
1756 1757
convergence, big network load and inability to handle larger networks
1757
makes it pretty much obsolete in IPv4 world. (It is still usable on
1758
very small networks.) It is widely used in IPv6 networks,
1759
because there are no good implementations of OSPFv3.
1758
makes it pretty much obsolete. (It is still usable on very small networks.)
1760 1759

  
1761 1760
<sect1>Configuration
1762 1761

  
......
1896 1895
implemented in future versions of BIRD:
1897 1896

  
1898 1897
<itemize>
1899
<item>OSPF for IPv6 networks
1900 1898
<item>OSPF NSSA areas and opaque LSA's
1901 1899
<item>Route aggregation and flap dampening
1902 1900
<item>Generation of IPv6 router advertisements
misc/bird.spec
1 1
Summary: BIRD Internet Routing Daemon
2 2
Name: bird
3
Version: 1.1.7
3
Version: 1.2.0
4 4
Release: 1
5 5
Copyright: GPL
6 6
Group: Networking/Daemons
nest/mrtdump.h
1 1
/*
2
 *	BIRD -- Password handling
2
 *	BIRD -- MRTdump handling
3 3
 *
4 4
 *
5 5
 *	Can be freely distributed and used under the terms of the GNU GPL.
......
13 13

  
14 14
#define MRTDUMP_HDR_LENGTH	12
15 15

  
16
/* MRTdump types */
17

  
16 18
#define BGP4MP			16
17 19

  
20
/* MRTdump subtypes */
21

  
18 22
#define BGP4MP_MESSAGE		1
19 23
#define BGP4MP_MESSAGE_AS4	4
20 24
#define BGP4MP_STATE_CHANGE_AS4	5
sysdep/config.h
7 7
#define _BIRD_CONFIG_H_
8 8

  
9 9
/* BIRD version */
10
#define BIRD_VERSION "1.1.7"
10
#define BIRD_VERSION "1.2.0"
11 11

  
12 12
/* Include parameters determined by configure script */
13 13
#include "sysdep/autoconf.h"

Also available in: Unified diff