]> git.puffer.fish Git - matthieu/frr.git/commit
zebra: nexthop groups vrf's are only a function of namespaces
authorDonald Sharp <sharpd@cumulusnetworks.com>
Mon, 13 Jan 2020 21:11:46 +0000 (16:11 -0500)
committerDonald Sharp <sharpd@cumulusnetworks.com>
Mon, 10 Feb 2020 13:04:19 +0000 (08:04 -0500)
commit1def701bae83a56e867206335c60d5bf237c96fe
treee79ea34e6cfad4d01624437cd380cb3649ecb2d9
parente83a19713dcb2d374defae560a499ae4d28ff475
zebra: nexthop groups vrf's are only a function of namespaces

Nexthop groups as a whole do not make sense to have a vrf'ness
As that you can have a arbitrary number of nexthops that point
to separate vrf's.

Modify the code to make this distinction, by clearly delineating
the line between the nhg and the nexthop a bit better.
Nexthop groups having a vrf_id only make sense if you are using
network namespaces to represent them.

Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
zebra/rt_netlink.c
zebra/zebra_nhg.c
zebra/zebra_nhg.h
zebra/zebra_vty.c