Re: KRT: Received route with strange next-hop

2015-12-05 Thread Brian Rak
On 12/5/2015 9:54 AM, Ondrej Zajicek wrote: On Sat, Nov 28, 2015 at 04:16:54PM -0500, Brian Rak wrote: 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

Re: KRT: Received route with strange next-hop

2015-12-05 Thread Ondrej Zajicek
On Sat, Nov 28, 2015 at 04:16:54PM -0500, Brian Rak wrote: > >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,

Re: KRT: Received route with strange next-hop

2015-11-28 Thread 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.

Re: KRT: Received route with strange next-hop

2015-11-25 Thread 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 th

Re: KRT: Received route with strange next-hop

2015-11-19 Thread 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: KRT: Received route 216.155.132.254/32 with strange next-hop 45.63.4.188 Netlink: Fi

Re: KRT: Received route with strange next-hop

2015-11-18 Thread 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: > > KRT: Received route 216.155.132.254/32 with strange next-hop > 45.63.4.188 > Netlink: File exists > > I have two routes relev

KRT: Received route with strange next-hop

2015-11-18 Thread Brian Rak
I'm trying to figure out why BIRD is throwing this error every time it scans the kernel routing table: KRT: Received route 216.155.132.254/32 with strange next-hop 45.63.4.188 Netlink: File exists I have two routes relevant to this one: # ip route | grep 45.63.4.188 45.63.4.188 dev veth0 s