summaryrefslogtreecommitdiffstats
path: root/vnet/vnet/ip/ip6.h
diff options
context:
space:
mode:
authorNeale <nranns@cisco.com>2016-07-01 13:00:09 +0100
committerDamjan Marion <dmarion.lists@gmail.com>2016-07-07 19:33:43 +0000
commite9dbd2b7819efdb2a3d2f92334c2e25849068e00 (patch)
treed576bc91e0dc7af186d0099cad41636144dccff3 /vnet/vnet/ip/ip6.h
parent689acafcabbc229a89cdbe5e628ca5e7a573afb2 (diff)
VPP-142 Recursive route sending traffic to wrong interface
Indirect routes should always result in an indriect adjacency even when the route's next-hop is covered by a connceted, since the covering route may change and no tracking is in place. Some de-duplication of code for installing indirect routes via the CLI and API. Change-Id: I7a440ffba43ae3990b68cb407244c06bd0827534 Signed-off-by: Neale <nranns@cisco.com>
Diffstat (limited to 'vnet/vnet/ip/ip6.h')
-rw-r--r--vnet/vnet/ip/ip6.h8
1 files changed, 8 insertions, 0 deletions
diff --git a/vnet/vnet/ip/ip6.h b/vnet/vnet/ip/ip6.h
index edeecdee8a6..22d1a4feaa0 100644
--- a/vnet/vnet/ip/ip6.h
+++ b/vnet/vnet/ip/ip6.h
@@ -389,6 +389,14 @@ void ip6_add_del_route_next_hop (ip6_main_t * im,
u32 next_hop_sw_if_index,
u32 next_hop_weight, u32 adj_index,
u32 explicit_fib_index);
+
+u32
+ip6_route_get_next_hop_adj (ip6_main_t * im,
+ u32 fib_index,
+ ip6_address_t *next_hop,
+ u32 next_hop_sw_if_index,
+ u32 explicit_fib_index);
+
u32
ip6_get_route (ip6_main_t * im,
u32 fib_index_or_table_id,