Never mind, it just crashed again :p
Jan 8 15:45:32 rr3 bird: Assertion '!old' failed at nest/rt-table.c:1497
Do you want a new coredump?
On Wed 08 Jan 2025 09:43:32 GMT, Alarig Le Lay via Bird-users wrote:
> Hello Maria,
>
> Thanks a lot, I confirm that it works well for me
or me), here is a fixed
> version:
> <https://gitlab.nic.cz/labs/bird/-/commit/2e14832d36c83b2ab5b7fb28b701de554fa5fdd9>
>
> If you could check that it works for you as well, it would be very helpful.
>
> Thank you for your report!
> Maria
>
> On Tue, Dec 31, 2024
ch appreciated, so I can try to
> > reproduce it.
> > Also would you say there is something unconventional about the said
> > setup that might be causing the problem?
> >
> > Thanks in advance and happy new year,
> >
> > David
> >
> > On 12/19/24 19:16
say there is something unconventional about the said
> setup that might be causing the problem?
>
> Thanks in advance and happy new year,
>
> David
>
> On 12/19/24 19:16, Alarig Le Lay via Bird-users wrote:
> > Hello Maria,
> >
> > I thought that I had the sam
Hello Maria,
I thought that I had the same bug, but it seems that it’s a different
one as I applied the patch but I still got a segfault at startup.
[342115.227497] bird[19396]: segfault at 8 ip 5642c37062db sp
7fc784295ca0 error 4 in bird[5642c366e000+f]
[342115.227524] Code: 39 10
On Mon 16 Dec 2024 17:23:46 GMT, Ondrej Zajicek wrote:
> Hello
>
> So if i undestand it correctly, if you put both 'min version 2' and
> 'max version 2', it failed? (that is expected if the peer does not support
> version 2)
My original goal was to feed the ASPA table, but the protocol was
negoti
Hello,
Following the 2.16 release with ASPA support, I tried to play with it.
So I tried to connect a bird instance to a RTR server with version 2 as
stated by https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.16
> The same protocol, since version 2, also receives and maintains a set
> of AS
On Mon 06 May 2024 18:02:28 GMT, Bastien Durel wrote:
> If I remember well, you must have a link-local address on the interface
> for it to be taken in account.
I confirm:
edge03-stolon ~ # ip a sh dev lo
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:0
Hello,
I have two OSPF protocols, one for IPv4 and one for IPv6. I’ve set the
lo interface for both, but it only shows up for IPv4:
protocol ospf ospf_ipv4 {
merge external;
ipv4 {
import all;
import keep filtered;
import limit 200
