Re: ibgp bird 1.6 vs 2.0

2019-04-30 Thread Matěj Grégr
On 30.04.2019 16:44, Ondrej Zajicek wrote: > On Tue, Apr 30, 2019 at 04:02:36PM +0200, Matěj Grégr wrote: >> >> >> 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

Re: ibgp bird 1.6 vs 2.0

2019-04-30 Thread Ondrej Zajicek
On Tue, Apr 30, 2019 at 04:02:36PM +0200, Matěj Grégr wrote: > > > 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

Re: ibgp bird 1.6 vs 2.0

2019-04-30 Thread Matěj Grégr
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

Re: ibgp bird 1.6 vs 2.0

2019-04-30 Thread Ondrej Zajicek
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

ibgp bird 1.6 vs 2.0

2019-04-30 Thread Matěj Grégr
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