Dear Ondrej, Am 25.09.10 18:49, schrieb Ondrej Zajicek: > On Wed, Sep 22, 2010 at 01:06:53PM +0200, Stefan Jakob wrote: ne route to get to the collector table: > > BGP1 - TABLE1 - COLLECTOR > BGP1 - TABLE1 - MASTER - TABLE2 - COLLECTOR > BGP1 - TABLE1 - MASTER - TABLE3 - COLLECTOR > ... > > The proper way to fix this is to add a filter on a pipe from a peer > table to the collector table to propagate only the routes from an > attached BGP protocol (and not the routes received transitively from > the master table).
I am wondering how such a filter would look like?: bird> show route table Collector where ! ( source = RTS_BGP) count 0 of 2561 routes for 1432 networks Guess source RTS_BGP isn't the answer, since imho all routes are originated from BGP? One solution might be to add an additional table to the protocol definition and use this table in the pipe going to the Collector table. Rgds, Stefan -- Stefan Jakob e-mail: stefan.ja...@de-cix.net DE-CIX Management GmbH Phone: +49 69 1730 902-32 Lindleystr. 12, 60314 Frankfurt Mobile: +49 172 695 8467 Geschaeftsfuehrer Harald A. Summa Fax: +49 69 4056 2716 Registergericht AG Koeln, HRB 51135 http://www.de-cix.net Zentrale: Lichtstr. 43i, 50825 Koeln