On Wed, Jan 27, 2010 at 04:49:45PM +0300, Mikhail A. Grishin wrote:
Handling of no-export community is hardcoded in BIRD, so such routes are not exported to the external neighbors, as it is expected. I can send you a patch that causes BIRD to ignore well-known communities (and leaves such behavior to configured filters) and we will make this behavior configurable in the next version.
Yes, it would be nice, please send me a patch. We expected that we could choose, which well-known communities must go through RS, which is not. Right now we only interested in transparency for "no-export".
Here is the patch that removes hardcoded handling of well-known communities. If you want the other well-known communities to work, you have to add appropriate code to export filters. -- 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."