BIRD trying to reinsert existing kernel routes, netlink issue?

[Zhaofeng Li]

I know this was an old thread, but would really appreciate if anyone is interested in digging in deeper. I can confirm the exact same behavior happens to me on NixOS with the 5.4.69 kernel but not on 4.19.149.

BIRD 2.0.7 on 5.4.69 would incessantly attempt to insert the same routes, rendering birdc unusable as it was presumably taking up so much time in the main loop (it was receiving an IPv4 full table over iBGP as well). While it was doing that, it stopped announcing the prefixes of stub interfaces to OSPF neighbors.

Thanks,
Zhaofeng Li

On Sun, Aug 2, 2020, at 17:36 PM, Sasha Romijn wrote:

> Hello,

> I’m running into a rather complex issue where BIRD tries to reinsert
routes into the kernel routing table that are already in there. I’m 
at the point of suspecting a netlink bug in the 5.x linux kernel.
However, I may be entirely off, and would like to hear what people with
more BIRD and/or netlink expertise think about it.

> My setup is bird 2.0.7 on Ubuntu 20.04. I’ve been able to reproduce
this with the default 5.4.0-42-generic kernel as well as the ubuntu
mainline 5.7.0-050700-generic kernel. This bird instance has an IBGP
peering with another bird 2.0.7 instance, which sends an IPv4 full
table. The IBGP peering is set up over a GRE tunnel. There is no other
routing software running. I am seeing this issue on another server too,
ubuntu 20.04 with 5.4.0-42-generic. A third one with ubuntu 18.04 and a
4.15.0-20-generic kernel, is fine.