Hello,
I think I found a bug in mrt_open_file & tm_format_real_time. On some of
my systems, mrt dump crashes if the filename pattern is longer than 42B.
Daemon dies with "*** stack smashing detected ***: terminated"
and no other fail messages are displayed.
I'm attaching gdb's bt full.
I took
Hello,
I was working recently with MRT dumps. I wrote a small patch that allows
bird to overwrite the dump file.
Piotr
--
Piotr 'GhosT' Wydrych Engineering Manager, SDN . Akamai
A: Because it messes up the
On 22.01.2021, 04:39, "Ondrej Zajicek" wrote:
> Thanks, fixed:
Works like a charm! Thanks for fix :-)
Piotr
Hello Ondrej,
On 14.01.2021, 04:03, "Ondrej Zajicek" wrote:
> Thanks for the bugreport. For IPv6 tables (due to ugliness of how MP-BGP
> handles bgp_nexthop), we forgot to generate fake MP_REACH_NLRI attribute
> with bgp_nexthop.
>
> The resulting files worked with bgpdump (which i used for tes
Robert,
On 09.11.2020, 11:39, "Robert Sander" wrote:
> You are able to filter on the protocol name which should identify the
> neighbor.
IIRC, you can filter on the incoming protocol name or type, not on the outgoing
one.
Piotr
