On Tue, Jan 19, 2010 at 12:56:04AM +0100, Ondrej Filip wrote:
# only guesswork here: I'm presuming this scans all dummy interfaces, and looks what is up and configured?
Yes
protocol direct { interface "dummy*"; }
protocol bgp { debug all; local as 65516; neighbor 192.168.1.2 as 3265; source address 192.168.1.1;
# again: guesswork, does this announce all 'protocol direct' stuff? export all;
Yes, it announces all routes from BIRD routing table, which is filled by routes from protocol direct.
}
My preference would be to explicitly list the prefixes that I want to announce, not having to rely on what I'm really configuring on my linux dummy interface. Is that coming, or did I misinterpret the docs?
Hi, of course you can specify export filters:
E.g.
=========== filter bgp_out { if (net = 192.175.48.0/24 ) then accept; else reject; }
protocol bgp { debug all; local as 65516; neighbor 192.168.1.2 as 3265; source address 192.168.1.1; export export filter bgp_out; ^^^^^^^^^^^^^ there should be just one 'export'
} ===========
But there is more way then just this one.
The other way is to not import routes from direct protocol, but explicitly specify them using static protocol. -- 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."