Dean Luga <dlug...@gmail.com> writes: > Hmm, I have been running babeld with source-specific routes for quite > some time and never run into this problem. Are you sure you didn't botch > the netlink calls? ;) > > I don't think so, I even tested inserting the routes with ip route > without running bird. It was a documented behavior in net/ipv6/Kconfig > in the kernel source.
Ah, I see. What was the specific route table entries that elicited this behaviour? And what kernel version? Will see if I can replicate it on my system... -Toke
