On 12/15/2015 6:41 AM, Ondrej Zajicek wrote:
On Mon, Dec 14, 2015 at 6:31 PM, d tbsky wrote:
2015-12-14 23:02 GMT+08:00 Shaun Crampton :
Hi,
I found a few messages in the archive that mention multi path and ECMP
but the website says it's TODO. I was just wondering what the status is?
I'm i
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 e
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
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
Ne
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
tting multiple/duplicate MD5 keys assigned to the TCP
session somehow?
-Mike
[1] https://patchwork.ozlabs.org/patch/138861/
On Tue, 25 Aug 2015 15:48:44 -0400
Brian Rak wrote:
I haven't tried the optmem_max option, but I did some more experimenting..
We have a virtual machine running a ne
:
echo 40960 > /proc/sys/net/core/optmem_max # Defaults to 20480
Which seemed to have deferred the issue, long enough for us to reboot /
not run into it constantly.
If anyone else has any details or info, I would still be interested in
the root-cause analysis and hopefully permanent fix.
-Mike
On
I have a machine running BIRD 1.4.5, and I'm seeing a lot of these
messages when I start it up:
2015-08-24 15:54:26 : Socket error: TCP_MD5SIG: Cannot
allocate memory
2015-08-24 15:54:26 : Socket error: TCP_MD5SIG: Cannot
allocate memory
It also seems like the sessions that report
