diff options
| author | Ondrej Zajicek <santiago@crfreenet.org> | 2012-11-16 02:34:12 +0100 |
|---|---|---|
| committer | Ondrej Zajicek <santiago@crfreenet.org> | 2012-11-16 02:34:12 +0100 |
| commit | cf3a704b6a2263aba6bb6adb4c2c9dd93b72f470 (patch) | |
| tree | 629ac0b8e6d7e5f28c92b7949dc600d2a7ffdc5d | |
| parent | 6cadbf325bfcf25a04d869778abb443f9e1b6119 (diff) | |
Updates the documentation.
| -rw-r--r-- | doc/bird.sgml | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/bird.sgml b/doc/bird.sgml index 7cea3921..d833f82f 100644 --- a/doc/bird.sgml +++ b/doc/bird.sgml @@ -1654,6 +1654,15 @@ use cases that use the direct protocol (like abusing eBGP as an IGP routing protocol), in most cases it is not needed to have these device routes in BIRD routing table and to use the direct protocol. +<p>There is one notable case when you definitely want to use the +direct protocol -- running BIRD on BSD systems. Having high priority +device routes for directly connected networks from the direct protocol +protects kernel device routes from being overwritten or removed by IGP +routes during some transient network conditions, because a lower +priority IGP route for the same network is not exported to the kernel +routing table. This is an issue on BSD systems only, as on Linux +systems BIRD cannot change non-BIRD route in the kernel routing table. + <p>The only configurable thing about direct is what interfaces it watches: <p><descrip> |