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
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
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
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
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
> reproducible with startup config.
>
> protocol static {
> ipv4 {};
> route 192
Hi,
It appears there is a segfault in the route specific filters, this was
initially observed during a `configure`, but appears to be easily
reproducible with startup config.
Environment:
OS: Ubuntu Focal/Xenial (from latest image on DockerHub)
GCC: 9.3.0 / 5.4.0
Bird: 2.0.7 (from https://bir
