On Mon, Oct 06, 2014 at 10:15:51AM -0400, micah wrote:
micah <micah@riseup.net> writes:
Some additional information, I do have a handful of static routes defined:
protocol static static_bgp { import all; route 204.13.164.0/24 reject; route 198.252.153.0/24 reject; route 199.254.238.0/24 reject; }
and these appear in bird as follows:
# birdc show route |grep '!' 204.13.164.0/24 unreachable [static_bgp 2014-10-04] ! (200) 198.252.153.0/24 unreachable [static_bgp 2014-10-04] ! (200) 199.254.238.0/24 unreachable [static_bgp 2014-10-04] ! (200)
which I understand is bird trying to add a route to the kernel, but it is already there.
Yes, that is exactly the reason for having 'Netlink: File exists' error message. BIRD does not rewrite routes that are already in kernel table from other sources. If you need them in kernel regardless of BIRD, you can as a workaround learn these routes from kernel proto and set them higher preference (using 'preference') than ones from static proto. That would prevent static routes to be exported to the kernel. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."