Hi Hans On Sun, 03 Mar 2013, Hans van Kranenburg wrote:
In this case, you can take advantage of the fact that you can create as many internal extra routing tables in bird for your own administration as you like, eliminating the 'bugging' extra filters you need when putting all in a single table. Using 'pipe' protocols you can import/export routes between the custom defined tables.
I'll have to study your suggested configuration and the pipe protocol before trying to apply it in production, but it sure looks nice :) Earlier today I had the following idea. Instead of specifying all static routes in the same protocol, as I did before, couldn't I define two instances and then filter based on the protocol name? # Prefixes to be exported to BGP procol static mynetworks { route a.b.c.0/24; route a.b.c.1/24; } # Route to the BGP peer protocol static bgp_peer_route { route w.z.y.x/32 via w.z.y.1; } protocol kernel { scan time 20; export where proto = "bgp_peer_route"; } This should work, right? Thanks a lot, Andre