Re: KRT: Received route with strange next-hop

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

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

Re: Socket error: TCP_MD5SIG: Cannot allocate memory

Ondrej Zajicek schrieb am Di., 25. Aug. 2015 23:11: On Tue, Aug 25, 2015 at 03:45:47PM -0500, Michael Vallaly wrote: > > For context on my end; this issue was experienced on physical hardware > (64bit) with Intel 1Gbit NICs (no offloading). > > We only noticed this after some length of time, (> 1