Setting BGP Aggregator Attribute in Filters

[Pavel Trefný]

Hi,

I have a question regarding BIRD. Is it possible to set the BGP 
aggregator attribute for a prefix using filters?

This would be useful in our anycast setup, where it can be difficult to 
determine the origin of a prefix. Using communities is unfortunately not 
a viable option for us — some of our hardware does not support extended 
communities, and upstream networks often filter them.

To clarify, I am not looking for route aggregation itself, but 
specifically a way to set the aggregator attribute.

Thank you for any insights.

Best regards,
Pavel Trefny


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20260414/3b5691fa/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x6F9565FDA7AFCAAB.asc
Type: application/pgp-keys
Size: 4439 bytes
Desc: OpenPGP public key
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20260414/3b5691fa/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20260414/3b5691fa/attachment.sig>