On Mon, May 31, 2010 at 10:17:52AM +0200, Arjan Filius wrote:

Hello,

Yet another question.

having configured debug like: debug protocols { states, routes , filters}; in the global section.

i see quite a lot messages on IPv4 and IPv6 bgp protocols: May 31 10:03:59 sbxbgpprd02 bird6: FiberRing_IPv6_111: Got UPDATE May 31 10:03:59 sbxbgpprd02 bird6: FiberRing_IPv6_111 > added 2001:40e8::/32 via 2a00:ec8::111 on fbr-ext--eth5 May 31 10:03:59 sbxbgpprd02 bird6: FiberRing_IPv6_111 < rejected by protocol 2001:40e8::/32 via 2a00:ec8::111 on fbr-ext--eth5

This is OK. You got the route from BGP, it was added to the table ('> added') and then it would be propagated to the other protocols, but protocol FiberRing_IPv6_111 rejected the route because it is its own route (therefore it shouldn't propagate it back to its peer). Other protocols (like kernel) didn't reject the route and accepted it. I think that this message about rejection of route back to the protocol that originated the route is confusing and uninformative, so we will probably remove it in the future. -- 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."