fix(rtable): Prevent direct send hairpins 76/276/3
authorE. Scott Daniels <daniels@research.att.com>
Thu, 6 Jun 2019 16:44:33 +0000 (16:44 +0000)
committerE. Scott Daniels <daniels@research.att.com>
Fri, 7 Jun 2019 16:26:03 +0000 (16:26 +0000)
If the current node is listed as an endpoint for a message type
that this process would add to the route table a hair-pin loop
back to the node can happen. This isn't desireable and this
change will prevent the current node from being added as a
recipient endpoint to any route table entry.

Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I5a1b2bdaad2eab499ae5a1c7430238c1da2f3256

Add latency call/receive test support

Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I70be670d063adfdf6505431a4a2ce72e846df0a4

Actual mods to implement hairpin loop avodiance

Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: Ieead4fbf69ade58db1f37d1949cf0f03683c64de
Signed-off-by: E. Scott Daniels <daniels@research.att.com>

No differences found