KRT: Received route with strange next-hop

[Ondrej Zajicek]

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.

-- 
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/20151119/50722c7a/attachment.asc>