Temporarily announcing more specific prefix?

[Robert Sander]

Hi Maximilian

On 21.09.20 20:59, Maximilian Wilhelm wrote:

> If the /24 is always present in the RIB why adding a static route for
> it?

Not all /24 are present in the RIB, some are.

> Just put another block into the BGP export filter for the /24 and
> guard it with a global variable, so you just have to change the global
> variable and "birdc c"
> 
> 
> # Somewhere global, maybe in an own file
> define MORE_SPECIFID = 0;
> 
> # Boiler plate export filter
> filter some_export_filter {
> 	# regular annonucement(s)
> 	if net ~ [ aaa/22 ] then
> 		accept;
> 
> 	if net ~ [ x/24 ] && MORE_SPECIFID = 1 then
> 		accept;
> 
> 	reject;
> }

Yes, that would be possible but would also make the filter rules more
complex.

I already implemented the "second table" idea with the pipe protocol and
it works. It just adds a few megabytes RAM because the FRT is stored
twice in the BIRD process. That does not matter when the router has 16GB
RAM. :)

Regards
-- 
Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin

https://www.heinlein-support.de

Tel: 030 / 405051-43
Fax: 030 / 405051-19

Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20200922/627cd796/attachment.sig>