On Thu, Mar 15, 2012 at 08:56:49PM +0100, Tomasz Głuch wrote:
On czw, mar 15, 2012 at 05:33:19 +0100, Benjamin Cama wrote:
Hi Thomasz,
Le jeudi 15 mars 2012 ?? 15:14 +0100, Tomasz Głuch a écrit :
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.
It's not that bird only allow static protocols, it's just that bird won't export device routes to kernel tables by default. See the ???device routes??? switch here http://bird.network.cz/?get_doc&f=bird-6.html#ss6.4 Thank you for help. Actually, enabling 'device routes' solved problem. I came across this term before, but I've change to many parameters at once to notice the difference.
Still, I don't understand why it even allows the static device route. Maybe because it's a host address?
According to argumentation from linked paragraph, static routes are not managed by kernel, so there is no reason to exclude them, but I could be wrong.
They are allowed because there is a no big risk of inadvertently mangling with kernel device routes if an user have to explicitly configure that device route in the static protocol. -- 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."