summaryrefslogtreecommitdiff
path: root/zebra/zebra_rib.c
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@nvidia.com>2022-02-28 13:08:01 -0500
committerDonald Sharp <sharpd@nvidia.com>2022-02-28 13:08:01 -0500
commit45dafca86cf68e7351be997351f2b1da623401a6 (patch)
treeb1c407da9ff889e7c9e3c0a0b459cae05e6c70c1 /zebra/zebra_rib.c
parentee95029ac41e1d3328e1409dcec477717a24a6f7 (diff)
zebra: Use the routes vrf not the vrf of the nexthop for route-map application
When a end operator is doing cross vrf imports in bgp: router bgp 3239 vrf FOO address-family ipv4 uni import vrf BAR ! and zebra has this configuration: vrf FOO ip protocol bgp route-map EVA ! The current code in zebra_nhg.c was looking up the vrf of the nexthop and attempting to apply the ip protocol route-map. For most people the nexthop vrf and the re vrf are one and the same so they never see a problem. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'zebra/zebra_rib.c')
0 files changed, 0 insertions, 0 deletions