diff options
| author | Donald Sharp <sharpd@cumulusnetworks.com> | 2020-01-13 16:11:46 -0500 |
|---|---|---|
| committer | Donald Sharp <sharpd@cumulusnetworks.com> | 2020-01-31 08:45:51 -0500 |
| commit | 88cafda739dcadeea13b671bfab6e8019968724e (patch) | |
| tree | 774a0a746998584fffa04bd1f70b399e7f0c0789 /zebra/zebra_nhg.h | |
| parent | 417f01b751f259577c9db14aa778d16c4d9e8d1e (diff) | |
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>
Diffstat (limited to 'zebra/zebra_nhg.h')
| -rw-r--r-- | zebra/zebra_nhg.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/zebra/zebra_nhg.h b/zebra/zebra_nhg.h index 522ec1e9dd..c2e173e094 100644 --- a/zebra/zebra_nhg.h +++ b/zebra/zebra_nhg.h @@ -195,7 +195,7 @@ extern int zebra_nhg_kernel_find(uint32_t id, struct nexthop *nh, vrf_id_t vrf_id, afi_t afi, int type, int startup); /* Del via kernel */ -extern int zebra_nhg_kernel_del(uint32_t id); +extern int zebra_nhg_kernel_del(uint32_t id, vrf_id_t vrf_id); /* Find via route creation */ extern struct nhg_hash_entry * |