I'm using bird 1.4.5 and I have a multihop bgp peer that I advertise a couple networks to, and they provide me with a full feed. My directly connected interface is configured like this: inet 208.99.192.142/30 brd 208.99.192.143 scope global eth3 but the neighbor config points to a different address (because its multihop): neighbor 208.99.192.121 as xxxx; it seems like I get this from them too: BGP.next_hop: 208.99.192.121 With this setup, I get these constant spammings in the logs: 2016-08-09 18:18:25 <WARN> Next hop address 208.99.192.121 resolvable through recursive route for 208.99.192.0/23 so did some reasearch and I managed to find this post[0] which suggested I add a static /32 so it can be resolved through a route that is not from BGP, so I did that: route 208.99.192.121/32 via 208.99.192.142%eth3; but then I get this flooding for every network I get from them: 2016-08-09 18:17:22 <ERR> KRT: Received route 223.255.210.192/26 with strange next-hop 208.99.192.142 so then I found this post[1], and so I tried: root@wren:/etc/bird# ip addr add 208.99.192.142 peer 208.99.192.121 dev eth3 but that didn't help... and bird seems to be eating a lot of CPU (100% of one CPU) when it wasn't doing that so much before. any ideas would be helpful! micah 0. http://bird.network.cz/pipermail/bird-users/2011-May/006842.html 1. http://bird.network.cz/pipermail/bird-users/2012-April/002990.html