BIRD (recursive acronym for BIRD Internet Routing Daemon^[2]) is a multithreaded open-source implementation for routing Internet Protocol packets on Unix-like operating systems. It was developed as a school project at the Faculty of Mathematics and Physics, Charles University, Prague,^[3] and is distributed under the GNU General Public License.

BIRD supports both Internet Protocol version 6 and version 4 in the same daemon.^[4] It establishes multiple routing tables,^[5] and uses BGP, RIP, OSPF and Babel routing protocols, as well as statically defined routes. Its design differs significantly from GNU Zebra, Quagga and FRRouting. BIRD has been included in many Linux distributions for long time, such as Debian,^[6] Ubuntu^[7] and Fedora.^[8]

BIRD is used in several Internet exchanges, such as the London Internet Exchange (LINX),^[9] LONAP,^[10] DE-CIX^[11] and MSK-IX^[12] as a route server, where it replaced Quagga because of its scalability issues.^[9] According to the 2012 Euro-IX survey,^[13] BIRD is the most used route server amongst European Internet exchanges.

In 2010, CZ.NIC, the current sponsor of BIRD development, received the LINX Conspicuous Contribution Award for contribution of BIRD to the advancement in route server technology.^[14]

Design

This section does not cite any sources. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (June 2022) (Learn how and when to remove this message)

BIRD implements multiple internal routing tables of various types to which the supported protocols connect. Most of these protocols import network routes to these internal routing tables and also export network routes from these internal routing tables to the given protocol. This way information about network routes is exchanged among different routing protocols.

Using the kernel protocol this internal routing table may be connected to the actual kernel routing table. This allows BIRD to export network routes from its internal routing table to the kernel routing table and optionally also learn about network routes from the kernel routing table (created externally by the administrator or by other means) and import these routes into its internal routing table.

Filters may be used to control what network routes are imported into the internal routing table or exported to the given protocol. Network routes may be accepted, rejected or modified using filters.

BIRD also supports multiple internal routing tables of the same type and multiple instances of supported protocol types. Protocols may be connected to different internal routing tables, these internal routing tables may exchange information about network routes they contain (controlled by filters) and each of these internal routing tables may be connected to a different kernel routing table thus allowing for policy routing.

Configuration is done by editing the configuration file and telling BIRD to reconfigure itself. BIRD changes to the new configuration without the need to restart the daemon itself and restarts reconfigured protocols only if necessary. There is also an option to do a soft reconfiguration, which doesn't restart protocols but may leave some stale information such as changed filters not filtering out already exported network routes.

See also

• List of open source routing platforms

References

External links

• Official website
• Bird Documentation
• Bloom-Bird: A Scalable Open Source Router Based on Bloom Filter