summaryrefslogtreecommitdiff
path: root/zebra/zebra_ns.c
diff options
context:
space:
mode:
authorPhilippe Guibert <philippe.guibert@6wind.com>2021-07-23 16:56:28 +0200
committerPhilippe Guibert <philippe.guibert@6wind.com>2021-09-21 18:37:30 +0200
commit42d4b30e00131923691ef260ed8b1ff11bf3f33c (patch)
tree2dbd7d0025c49dfe2605f53ad4d89fcf0fe57212 /zebra/zebra_ns.c
parentf334c88ed9675eab624728ecd6eaaff3a9b41255 (diff)
zebra: extend table manager per vrf, add vty configuration
Because vrf backend may be based on namespaces, each vrf can use in the [16-(2^32-1)] range table identifier for daemons that request it. Extend the table manager to be hosted by vrf. That possibility is disabled in the case the vrf backend is vrflite. In that case, all vrf context use the same table manager instance. Add a configuration command to be able to configure the wished range of tables to use. This is a solution that permits to give chunks to bgp daemon when it works with bgp flowspec entries and wants to use specific iptables that do not override vrf tables. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
Diffstat (limited to 'zebra/zebra_ns.c')
-rw-r--r--zebra/zebra_ns.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/zebra/zebra_ns.c b/zebra/zebra_ns.c
index 27b8a3ea47..0f53de8c31 100644
--- a/zebra/zebra_ns.c
+++ b/zebra/zebra_ns.c
@@ -127,9 +127,6 @@ int zebra_ns_enable(ns_id_t ns_id, void **info)
route_read(zns);
kernel_read_pbr_rules(zns);
- /* Initiate Table Manager per ZNS */
- table_manager_enable(ns_id);
-
return 0;
}
@@ -142,8 +139,6 @@ static int zebra_ns_disable_internal(struct zebra_ns *zns, bool complete)
kernel_terminate(zns, complete);
- table_manager_disable(zns->ns_id);
-
zns->ns_id = NS_DEFAULT;
return 0;