KRT: Received route with strange next-hop

[Brian Rak]

On 11/25/2015 5:51 AM, Ondrej Zajicek wrote:
> On Thu, Nov 19, 2015 at 08:25:01AM -0500, Brian Rak wrote:
>>> 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.
> Hi
>
> Sorry for late answer, 'device route' i call a route for directly
> attached network prefix, with associated iface but without associated
> gateway IP. Perhaps there is a better / more established term for such
> routes.
>
Sorry, my spam filter was delaying this.

That's what I have I think?  I have the '45.63.4.188 dev veth0 scope 
link' route, I'm not aware of any other way to add this (and it doesn't 
use a gateway IP).  Are you talking about the '216.155.132.254 via 
45.63.4.188 dev veth0 proto bird' route?  If so, I have no way to  
change that.  BIRD itself is adding that route based on information from 
BGP. AFAIK, there is no way to specify the next hop is an interface via BGP.