KRT: Received route with strange next-hop

[Brian Rak]

On 11/19/2015 2:52 AM, Ondrej Zajicek wrote:
> On Wed, Nov 18, 2015 at 01:01:44PM -0500, Brian Rak wrote:
>> I'm trying to figure out why BIRD is throwing this error every time it scans
>> the kernel routing table:
>>
>> <ERR> KRT: Received route 216.155.132.254/32 with strange next-hop
>> 45.63.4.188
>> <WARN> Netlink: File exists
>>
>> I have two routes relevant to this one:
>>
>> # ip route | grep 45.63.4.188
>> 45.63.4.188 dev veth0 scope link
>> 216.155.132.254 via 45.63.4.188 dev veth0 proto bird
>>
>> The 45.63.4.188 route was added by me (manually), the 216.155.132.254 was
>> added via BIRD (BIRD learned it via BGP).
> Hi
>
> Generally, BIRD expects that the next hop address is reachable by
> interface address prefix. In your case you just add device route for
> 45.63.4.188/32 instead of adding peer address of 45.63.4.188 to veth0. It
> is true that for the kernel the difference does not matter in this
> regard and that the warning is not important in this case.

What do you mean by 'device route'?  I'm not sure how that differs from 
what I have, and not finding a lot of references to that phrase online.