From e9dbd2b7819efdb2a3d2f92334c2e25849068e00 Mon Sep 17 00:00:00 2001 From: Neale Date: Fri, 1 Jul 2016 13:00:09 +0100 Subject: 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 --- vpp-api-test/vat/api_format.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'vpp-api-test/vat') diff --git a/vpp-api-test/vat/api_format.c b/vpp-api-test/vat/api_format.c index 6b5271dd039..d4bc27bda8a 100644 --- a/vpp-api-test/vat/api_format.c +++ b/vpp-api-test/vat/api_format.c @@ -4269,7 +4269,7 @@ static int api_ip_add_del_route (vat_main_t * vam) unformat_input_t * i = vam->input; vl_api_ip_add_del_route_t *mp; f64 timeout; - u32 sw_if_index = 0, vrf_id = 0; + u32 sw_if_index = ~0, vrf_id = 0; u8 sw_if_index_set = 0; u8 is_ipv6 = 0; u8 is_local = 0, is_drop = 0; -- cgit 1.2.3-korg