Re: bird-1.5.0 ipv4 segfaults on configure - is it safe to change bgp protocol names runtime?

18 Mar 2016


      On 03/18/2016 10:44 AM, Jan Matejka wrote:
...
On 03/18/2016 10:28 AM, Bartosz Radwan wrote:
...
On 18.03.2016 10:07, Jan Matejka wrote:
...
Can you please send in a reduced config set that still causes this bug?
I'd like to reproduce it locally and fix it thereafter.
Thanks a lot.
Minimal config causing the errors:
protocol direct {
interface "br0.*", "br1", "br1.*";
        debug all;
}
protocol kernel {
        learn;
        persist;
        scan time 1;
        export all;
}
protocol device {
        scan time 1;
}
protocol bgp one {
router id 10.13.0.31;
    debug all;
    next hop self;
    direct;
    import none;
    export filter { if net = 10.10.10.0/24 then {accept;  accept; }
reject; };
    local 10.13.0.1 as 65532;
    neighbor 10.13.0.2 as 65531;
    check link 1;
}
Thanks!
I'm unable to reproduce it at fresh built bird-1.5.0 from Git. But I
don't have any traffic at the BGP and the segfault may come from it (we
know about another issue which may be related). Maybe … does it occur
even if you just restart the BGP protocol from birdc?

JM