-
Bug
-
Resolution: Done
-
Medium
-
17.10
-
None
-
None
Both single hop and multi hop options when adding a route does not work correctly when we need to create a route which will forward the traffic to another table. It happens because there is always a nextHop specified. But for a route with lookup in different table there shouldnt be any next hops only the secondary VRF id. See the attached file for simpleNext hop API call that HC is configuring on VPP
- relates to
-
VPP-994 ip_fib_dump does not contain paramterer lookup_in_table
-
- Closed
-
-
HC2VPP-233 Support lookup in secondary table for routing directly in model
-
- To Do
-