Re: BIRD trying to reinsert existing kernel routes, netlink issue?

[Alarig Le Lay]

Hi Sasha,

On Sun 02 Aug 2020 17:36:13 GMT, Sasha Romijn wrote:
> protocol kernel {
>     scan time 20;
>     ipv4 {
>         export all;
>         import none;
>     };
> }

I think that the issue is there, you’re not importing routes from the
kernel, so bird doesn’t know that they exist, but you export all routes
to it. So it ends up by resending an already existing route.

And for example, on my of my routers :
bird> show route all 80.213.72.0/22
Table master4:
80.213.72.0/22       unicast [direct1 2020-07-24] * (240)
        dev enp2s0
        Type: device univ
                     unicast [kernel_grt_ipv4 2020-07-24] (10)
        dev enp2s0
        Type: inherit univ
        Kernel.source: 16
        Kernel.metric: 3
        Kernel.prefsrc: 80.213.74.176
        Kernel.scope: 253

This route is learned from both direct1 and kernel_grt_ipv4, so it would
be re-sent to the kernel if I remove the "import all".

Regards,
-- 
Alarig