cc315f356693cba1402ad1c259585b03ad861960
howto/Bird2.md
| ... | ... | @@ -6,7 +6,7 @@ The `extra/bird` package in the arch repositories will usually have a relatively |
| 6 | 6 | |
| 7 | 7 | ## Bird2 Version <2.0.8 / Debian |
| 8 | 8 | |
| 9 | -Please note, that Bird2 versions before 2.0.8 don't support IPv6 extended nexthops for IPv4 destinations (<https://bird.network.cz/pipermail/bird-users/2020-April/014412.html>). |
|
| 9 | +Please note, that Bird2 versions before 2.0.8 don't support IPv6 extended next hop for IPv4 destinations (<https://bird.network.cz/pipermail/bird-users/2020-April/014412.html>). |
|
| 10 | 10 | Additionally Bird2 before 2.0.8 cannot automatically update filtered bgp routes when a used RPKI source changes. |
| 11 | 11 | |
| 12 | 12 | Debian 11 Bullseye delivers Bird 2.0.7. But you can use the Debian Bullseye backport-repository which provides version 2.0.8 (see <https://backports.debian.org/Instructions/> for adding backports repository and install packages from the repository). |
| ... | ... | @@ -437,7 +437,7 @@ protocol rpki rpki_dn42{ |
| 437 | 437 | ``` |
| 438 | 438 | ### Use BFD in bird2 |
| 439 | 439 | BFD is an additional protocol to detect failures in the switching plane between peers, |
| 440 | -it is used widely by cleanet peerings and some networks in DN42 already have enabled it globally. |
|
| 440 | +it is used widely by clearnet peerings and some networks in DN42 already have enabled it globally. |
|
| 441 | 441 | To do a basic configuration you need to add 1 line to your bird.conf and enable it per peer or globally by defining it in the |
| 442 | 442 | template. |
| 443 | 443 | It is currently recommended that you only enable it for each peer that supports it and has it enabled. |