|
|
# BIRD FAQ
|
|
|
|
|
|
### Which OS distributions are supported?
|
|
|
|
|
|
We test BIRD on CentOS 7, Debian 8, Debian 9, FreeBSD 11, OpenBSD 5.8 and NetBSD 7.
|
|
|
Sometimes we run also FreeBSD 10, CentOS 6 and Debian 7 and it also seems to work there well.
|
|
|
|
|
|
Limited support is possible for Android (7.1) in Termux app; we don't test it much.
|
|
|
|
|
|
We think it may run at DragonflyBSD and probably other BSD systems quite well.
|
|
|
We never tested BIRD at Mac OS X. If it works, let us know; if not, send a patch!
|
|
|
|
|
|
We currently don't support Windows. There were [some efforts to manage it](http://trubka.network.cz/pipermail/bird-users/2018-May/012342.html) but no patch has been sent yet.
|
|
|
|
|
|
### How BIRD handles IPv6?
|
|
|
|
|
|
BIRD has an unusual way to handle IPv6. BIRD can be compiled to support either IPv4, or IPv6. Distributions have different packages for both versions of BIRD. To route both protocols, you have to use two completely separated bird processes, with two separate config files (usually _bird.conf_ and _bird6.conf_). Therefore, it is impossible to have one BGP session propagating both IPv4 and IPv6 prefixes.
|
|
|
In version 1.x, BIRD has an unusual way to handle IPv6. BIRD can be compiled to support either IPv4, or IPv6. Distributions have different packages for both versions of BIRD. To route both protocols, you have to use two completely separated bird processes, with two separate config files (usually _bird.conf_ and _bird6.conf_). Therefore, it is impossible to have one BGP session propagating both IPv4 and IPv6 prefixes.
|
|
|
|
|
|
In version 2, BIRD can handle both IPv4 and IPv6 (and also other address families / AFIs / SAFIs) in one process.
|
|
|
|
|
|
### OSPF and multiple ptp addresses on one interface
|
|
|
|
... | ... | @@ -19,6 +33,7 @@ First, _learn_ option of kernel protocol must be active. |
|
|
Second, 'device' routes related to interface addresses/prefixes added automatically by OS/kernel are never imported. You could add them using _direct_ protocol.
|
|
|
|
|
|
Third, for some obscure and historic reasons BIRD 1.3.x (or older) does not import even some manually added device/host routes (i.e. ones without gateway). There are two ways to fix this. Either add these routes to the kernel routing table with _static_ protocol source (e.g. '@ip route add 10.20.30.0/24 dev eth0 proto static@' ), or recompile BIRD with attached patch (see the bottom of the page) to fix this issue.
|
|
|
Anyway, first try some newer version than 1.3 if possible.
|
|
|
|
|
|
### IPv6 blackhole and prohibit routes do not work on Linux
|
|
|
|
... | ... | |