ibgp bird 1.6 vs 2.0

Matěj Grégr mgregr at fit.vutbr.cz
Tue Apr 30 16:02:36 CEST 2019



On 30.04.2019 15:56, Ondrej Zajicek wrote:
> On Tue, Apr 30, 2019 at 03:34:59PM +0200, Matěj Grégr wrote:
>> Hello,
>>   we have encountered a different ibgp behavior between bird 1.6 and
>> bird2, and I am not sure if it's an intentional change in bird2 or a
>> bug. Let's consider the following topology:
>>
>>       192.168.1.0/24           192.168.2.0/24
>>  R1 ------- ebgp ------- R2 ------- ibgp ------- R3
>>    .2                 .1   .1                  .2
>>
>> R1 uses AS 65001, R2 and R3 uses AS 65000. R1 propagates some routes
>> (e.g. 10.10.10.0/24) via eBGP to R2, which sends them to R3 via iBGP.
>> bird2 config on R3:
>>
>> template bgp IBGP {
>>         local as 65000;
>>         direct;
>>         ipv4 {
>>                 next hop self;
>>                 import keep filtered on;
>>                 import all;
>>         };
>> }
>>
>> protocol bgp from IBGP { neighbor 192.168.2.1 as 65000; }
> 
> What bird is config on R2?
> 
> I don't think there are any intentional changes w.r.t. your config.
> 

R2 is not running bird, but it's a cisco router, but we encounter the
same behavior with other vendors as well (HP). The config is pretty
simple on R2:

router bgp 65000
 bgp log-neighbor-changes
 network 192.168.1.0
 network 192.168.2.0
 neighbor 192.168.1.1 remote-as 65001
 neighbor 192.168.2.2 remote-as 65000

The routes are correctly sent from R2 to R3 (checked it with tcpdump and
routes are included in BGP updates)

M.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2929 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20190430/5e2c4b8b/attachment.p7s>


More information about the Bird-users mailing list