]> git.proxmox.com Git - mirror_frr.git/commit
bgpd: No nexthop tracking for EVPN-imported leaked routes
authorvivek <vivek@cumulusnetworks.com>
Thu, 28 Feb 2019 11:11:01 +0000 (11:11 +0000)
committervivek <vivek@cumulusnetworks.com>
Thu, 28 Feb 2019 11:11:01 +0000 (11:11 +0000)
commit0a2f9ac170f19a8739146838120a1518cd370029
tree94b1b7cb1239951381efbf19901daec7aae3783a
parent12d6100c52d14f7501cd04ffbb6a4f1b10ec3cd6
bgpd: No nexthop tracking for EVPN-imported leaked routes

IPv4 or IPv6 unicast routes which are imported from EVPN routes
(type-2 or type-5) and installed in a BGP instance and then leaked
do not need any nexthop tracking, as any tracking should happen in
the source instance.

Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com>
Reviewed-by: Anuradha Karuppiah <anuradhak@cumulusnetworks.com>
Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com>
bgpd/bgp_evpn.h
bgpd/bgp_mplsvpn.c
bgpd/bgp_route.h