Next-hop check not needed?

[Vincent Bernat]

 ❦ 28 juin 2017 14:01 +0200, Ondrej Zajicek <santiago at crfreenet.org> :

> Note that when learning route from the kernel you could workaround it by
> using 'onlink' route flag.

Great!

It seems to work:

$ ip route show table public dev eth2
203.0.113.1 scope link metric 10
203.0.113.10 via 203.0.113.1 metric 10 onlink

bird> show route table public
203.0.113.10/32    via 203.0.113.1 on eth2 [kernel_public 15:58:09] * (200)
203.0.113.1/32     dev eth2 [kernel_public 15:58:09] * (200)

But BIRD (1.6.3) still seems to be a bit confused, since I got this
message in a loop:

2017-06-28 16:01:20 <ERR> KRT: Received route 203.0.113.10/32 with strange next-hop 203.0.113.1
2017-06-28 16:01:20 <WARN> Netlink: File exists

Other than that, everything works as expected. I don't know how to
interpret the first message (is it receiving two routes?) but the second
message seems to say that it tries to reinstall the same route it
received.
-- 
10.0 times 0.1 is hardly ever 1.0.
            - The Elements of Programming Style (Kernighan & Plauger)