route attribute scope

[Ondrej Zajicek]

On Fri, Jun 20, 2014 at 01:45:47PM +0200, Frederik Kriewitz wrote:
> Hello,
> 
> we noticed something which feels like an inconsistency/bug to us.
> 
> So far we assumed that route attributes can be set in any filter of
> any protocol.
> But it seems like OSPF attributes can be set only in export filters of
> OSPF protocols.

Hello

This is known inconsistency/quirk. It is is a result of current
attribute implementation (where EAF_EMBEDDED attributes are stored
directly in struct rte instead of in extended attribute list). Redesign
of embedded attributes (to fix this problem and also to simplify it)
is in my todo list.

The current behavior is that regular attributes (e.g. ones from BGP)
could be set anywhere, while embedded attributes (ones from OSPF, RIP
and KRT) could be set either in export filter to 'their' protocol, or
anywhere for 'their' routes (i.e. you could set ospf_metric1 anywhere
for route received from OSPF, with source == RTS_OSPF, but that is
probably not much useful).

-- 
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/20140620/2aff5c37/attachment-0001.asc>