Announce prefix to BGP conditional
Alexander V. Chernikov
melifaro at ipfw.ru
Fri Jan 4 00:34:43 CET 2013
On 04.01.2013 03:17, Robert Hass wrote:
>> Patch is available at
>> http://static.ipfw.ru/patches/0001-Implement-general-aggregation-protocol-v6.patch
>>
>> We run this protocol on a large route-reflector for a while without any
>> issues, but YMMV.
>
> Hi
>
> I applied patch in my bird, but it look's it's not working. My
> configuration bird.conf:
>
> log syslog { debug, trace, info, remote, warning, error, auth, fatal, bug };
> router id 10.0.0.3;
>
> protocol device {
> scan time 60;
> }
>
> protocol aggregator AG1 {
> import all;
> bgp id 10.0.0.2 as 100 {
> aggregate address 1.1.1.2/32;
> aggregate address 1.1.1.1/32 mandatory list { 10.44.0.0/24 };
> };
> }
You still have to announce at least one route within aggregate-address
block (so /32 setup won't work, at least /31 prefix).
E.g. configuration should look like
aggregate address 1.1.1.1/30 mandatory list { 10.44.0.0/24 };
and you are required to have
1.1.1.1/32 AND 10.44.0.0/24 to be in your route table to make
aggregation protocol announce given route.
This is probably not obvious from examples/docs :(
>
> protocol bgp CISCO {
> local as 300;
> source address 10.0.0.3;
> neighbor 10.0.0.4 as 400;
> import filter bgp_cust_in;
> export filter {
> if (net ~ [1.1.1.1/32] ) then {
> accept;
> }
> if (net ~ [1.1.1.2/32]) then {
> accept;
> }
> };
> }
>
>
> bird> show route
> 10.44.0.0/24 via 10.0.0.4 on em1 [CISCO 00:04] * (100) [AS400i]
> bird>
>
> Any comments ?
>
> Rob
>
More information about the Bird-users
mailing list