On 05.12.2015 16:01, Ondrej Zajicek wrote:
Well, it is a bug (fixed in devel branch), not intended behavior
Thanks Ondriej.
When approximately next stable release including this fix is expectded?
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting su
On Tue, Dec 01, 2015 at 11:53:55AM +0100, Bartosz Radwan wrote:
> I have similiar config on my Linux router, but in my case source address
> exists until i shut the interface down.
> When the interface is shut down (ifdown interfacename), bird crashes.
>
> May be dangerous, i could imaginge situat
On 18.07.2015 15:14, Michal Humpula wrote:
Thanks for the hint! The crashing after inability to allocate socket,
got me thinking that it only occurs only in one connection and only on
one instance. So yeah, I've got something silly like this in my setup:
protocol bgp test {
neighbor 10.0.1.2
Thanks for the hint! The crashing after inability to allocate socket,
got me thinking that it only occurs only in one connection and only on
one instance. So yeah, I've got something silly like this in my setup:
protocol bgp test {
neighbor 10.0.1.2 as 1;
source address 10.1.1.1;
bfd 1;
}
On Fri, Jul 17, 2015 at 03:22:45PM +0200, Michal Humpula wrote:
> Hi,
>
> I came across this lovely segfault when using BFD in Bird v1.4.5 and v1.5:
>
> (gdb) bt
> #0 bfd_send_ctl (p=0x557cf840, s=0x557e2cf8, final=0) at
> ../../../proto/bfd/packets.c:66
> #1 0x5556fc86 in timer
Hi,
I came across this lovely segfault when using BFD in Bird v1.4.5 and
v1.5:
(gdb) bt
#0 bfd_send_ctl (p=0x557cf840, s=0x557e2cf8, final=0) at
../../../proto/bfd/packets.c:66
#1 0x5556fc86 in timers_fire (loop=loop@entry=0x557dfba0)
at ../../../proto/bfd/io.c:437
#2
