KRT: Received route with strange next-hop

[Ondrej Zajicek]

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.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at 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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20151125/4a72df28/attachment.asc>