bird 2.0.3 pushes connected routes to kernel
After upgrading from bird 2.0.2 to 2.0.3 we discovered that bird pushes connected routes to the kernel. Tried to alter the preference values for kernel and device, but bird still pushes the connected routes, resulting in duplicate in kernel FIB. How to import connected and kernel routes without bird installing the connected routes again? The only way I found to make it work was by putting an export filter in the kernel like this; export where (source != RTS_DEVICE); Thanks, Kenth
On Thu, Feb 14, 2019 at 02:28:52PM +0000, Kenth Eriksson wrote:
After upgrading from bird 2.0.2 to 2.0.3 we discovered that bird pushes connected routes to the kernel. Tried to alter the preference values for kernel and device, but bird still pushes the connected routes, resulting in duplicate in kernel FIB.
How to import connected and kernel routes without bird installing the connected routes again? The only way I found to make it work was by putting an export filter in the kernel like this; export where (source != RTS_DEVICE);
Yes, there is no longer a special case for device routes in kernel protocol. Although the change was done in 2.0.0, so should be the same for 2.0.2 and 2.0.3. Using export filter like 'export where source != RTS_DEVICE;' makes sense. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (2)
-
Kenth Eriksson -
Ondrej Zajicek