Hello Marek,
this looks fishy. We haven't yet had an opportunity to properly test the
Netlink at FreeBSD so thank you for reporting, this is indeed a bug.
As soon as we get to spin up the newest FreeBSD, we'll look into it and
try to debug.
Thank you for your report!
Maria
Dear BIRD Developers,
I have tested the Netlink flavor of FreeBSD port. At a glance there are
at least 2 problems:
1. Memory (resident) usage at the init is about 125% of BIRD 2.13,
moreover it's constantly growing and after 30 min it was about 300% of
shown by BIRD 2.13.
2. Some routes are not learned correctly, for example:
Apr 27 20:20:23 rtr bird[40469]: bgp_rmsk_v4: Invalid route x.y.140.0/22
withdrawn
Apr 27 20:20:23 rtr bird[40469]: bgp_rmsk_v4: Invalid route x.y.160.0/22
withdrawn
Apr 27 20:20:23 rtr bird[40469]: bgp_rmsk_v4: Invalid route x.y.184.0/22
withdrawn
Apr 27 20:20:23 rtr bird[40469]: bgp_rmsk_v4: Invalid route y.y.184.0/24
withdrawn
Apr 27 20:20:23 rtr bird[40469]: bgp_rmsk_v4: Malformed bgp_unknown_0x15
attribute - conflicting flags (e0, expected 80)
Apr 27 20:20:23 rtr bird[40469]: bgp_rmsk_v4: Malformed bgp_unknown_0x15
attribute - conflicting flags (e0, expected 80)
Apr 27 20:20:23 rtr bird[40469]: bgp_rmsk_v4: Malformed bgp_unknown_0xff
attribute - conflicting flags (e0, expected 80)
Apr 27 20:20:23 rtr bird[40469]: bgp_rmsk_v4: Malformed bgp_unknown_0xff
attribute - conflicting flags (e0, expected 80)
It came out, that in BIRD 2.13 at least some of these problematic routes
have special attributes, for example:
BGP.ff [t]: 00 00 07 db 00 00 00 01 00 01 00 0a ff 08 00 00 00 00 ea 44
42 79
Thanks for giving the opportunity to test !
Cheers
