Re: [PATCH] Nest: Read Babel metric as IGP metric

2020-12-28 Thread Ondrej Zajicek
On Mon, Dec 28, 2020 at 05:05:07PM -0800, James Lu wrote: > Hello, > > Can someone take a look at this? It's a pretty simple patch but a patch > nonetheless, so it'd be great if this was fixed upstream. Hello Thanks, merged [*]. Sorry, forgot about that. [*] https://gitlab.nic.cz/labs/bird/-/c

Re: [PATCH] Nest: Read Babel metric as IGP metric

2020-12-28 Thread James Lu
Hello, Can someone take a look at this? It's a pretty simple patch but a patch nonetheless, so it'd be great if this was fixed upstream. Best, James On 2020-08-16 1:58 p.m., James Lu wrote: > Hi all, > > When testing Babel with Bird 2.0.7, I noticed that unlike OSPF, Babel > metrics are not rea

Re: BIRD 2.0.7 segfault in route filters

2020-12-28 Thread Damian Zaremba
On 28/12/2020 15:06, Ondrej Zajicek wrote: On Mon, Dec 28, 2020 at 04:29:25AM +0100, Ondrej Zajicek wrote: On Sun, Dec 27, 2020 at 09:58:57PM +0100, Damian Zaremba wrote: Hi, It appears there is a segfault in the route specific filters, this was initially observed during a `configure`, but ap

Re: BIRD 2.0.7 segfault in route filters

2020-12-28 Thread Ondrej Zajicek
On Mon, Dec 28, 2020 at 07:23:51PM +0100, Ondrej Zajicek wrote: > On Mon, Dec 28, 2020 at 06:47:29PM +0100, Damian Zaremba wrote: > > Hi, > > > > Thanks for the fast response and fix - I can confirm that is working as > > expected on my side. > > > > Unfortunately I did discover another segfault

Re: BIRD 2.0.7 segfault in route filters

2020-12-28 Thread Ondrej Zajicek
On Mon, Dec 28, 2020 at 06:47:29PM +0100, Damian Zaremba wrote: > Hi, > > Thanks for the fast response and fix - I can confirm that is working as > expected on my side. > > Unfortunately I did discover another segfault (testing from current master) > which appears to be due to `net` being uniniti

Re: BIRD 2.0.7 segfault in route filters

2020-12-28 Thread Ondrej Zajicek
On Mon, Dec 28, 2020 at 04:29:25AM +0100, Ondrej Zajicek wrote: > On Sun, Dec 27, 2020 at 09:58:57PM +0100, Damian Zaremba wrote: > > Hi, > > > > It appears there is a segfault in the route specific filters, this was > > initially observed during a `configure`, but appears to be easily > > reprodu