On Thu, Oct 15, 2009 at 02:46:53PM +0100, David J Craigon wrote:
Ace, thanks for that.
How do I aggregate prefixes for export, so that rather than export lots of small prefixes, I can just export one big prefix? I'm guessing bird is just getting all of the routes it knows about and exporting them one-by-one (so lots of really small routes) rather than one big one.
Alternatively, is there a way of overriding what gets sent, so I can just manually send one big route?
Automatic aggregation is not implemented in BIRD. Required behavior can be achieved by defining static route for one big prefix and then export just that route to BGP. Configured static route could use 'unreachable' target, as such route target is not propagated through BGP (it is propagated as a normal prefix) and such route might be useful in local routing table. For example: protocol static { import all; route xxx.yyy.0.0/16 unreachable; } protocol bgp { import all; export where net = xxx.yyy.0.0/16; } or 'export where net ~ [xxx.yyy.0.0/16, xxx.zzz.0.0/16, ...];' if there is more configured prefixes to export. or 'export where source = RTS_STATIC;' if every static route should be exported through BGP. -- 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."