diff options
| author | vivek <vivek@cumulusnetworks.com> | 2019-03-01 07:10:53 +0000 |
|---|---|---|
| committer | vivek <vivek@cumulusnetworks.com> | 2019-03-01 07:10:53 +0000 |
| commit | 744c63be132a4644c7c3799a0f0d2a07bfc5b98a (patch) | |
| tree | 6113e91b538701552c1b58039a5bf7786892a14d /zebra/zapi_msg.c | |
| parent | 9544ddb28842e5e73e86880f3b12fa52bf264817 (diff) | |
zebra: Use next hop's VRF for EVPN-based routes
Ensure that the next hop's VRF is used for IPv4 and IPv6 unicast routes
sourced from EVPN routes, for next hop and Router MAC tracking and
install. This way, leaked routes from other instances are handled properly.
Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com>
Reviewed-by: Anuradha Karuppiah <anuradhak@cumulusnetworks.com>
Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'zebra/zapi_msg.c')
| -rw-r--r-- | zebra/zapi_msg.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/zebra/zapi_msg.c b/zebra/zapi_msg.c index 9b91289dec..ef9917d4e6 100644 --- a/zebra/zapi_msg.c +++ b/zebra/zapi_msg.c @@ -1463,8 +1463,8 @@ static void zread_route_add(ZAPI_HANDLER_ARGS) &(api_nh->gate.ipv4), sizeof(struct in_addr)); zebra_vxlan_evpn_vrf_route_add( - vrf_id, &api_nh->rmac, &vtep_ip, - &api.prefix); + api_nh->vrf_id, &api_nh->rmac, + &vtep_ip, &api.prefix); } break; case NEXTHOP_TYPE_IPV6: @@ -1493,8 +1493,8 @@ static void zread_route_add(ZAPI_HANDLER_ARGS) memcpy(&vtep_ip.ipaddr_v6, &(api_nh->gate.ipv6), sizeof(struct in6_addr)); zebra_vxlan_evpn_vrf_route_add( - vrf_id, &api_nh->rmac, &vtep_ip, - &api.prefix); + api_nh->vrf_id, &api_nh->rmac, + &vtep_ip, &api.prefix); } break; case NEXTHOP_TYPE_BLACKHOLE: |