exporting routes to kernel

[Ondrej Zajicek]

On Thu, Mar 15, 2012 at 03:14:31PM +0100, Tomasz Głuch wrote:
> Is there any reason to not accept routes other than RTS_STATIC_DEVICE, assuming that
> possible loops are filtered out? Is other approach for this issue? The same problem occurs
> when routes origin from OSPF.

This is here mainly to prevent people from inadvertently overwriting
kernel supplied device routes (which could be easily done if you just
export all routes to kernel and have device routes from direct or OSPF
in the table). When BIRD goes down, it cleans up its routes so it would
left the system in not really working state.

You could use 'device routes' kernel option (which is the
KRT_CF->devroutes condition) to disable it. Perhaps we should add some
warning here. Or we should apply that only for main kernel table, where
kernel device routes are.

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at 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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20120319/fc3c8510/attachment-0001.asc>