summaryrefslogtreecommitdiffstats
path: root/zebra/zebra_vrf.h
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_vrf.h
parentMerge pull request #9581 from idryzhov/rpki-source-move (diff)
downloadfrr-42d4b30e00131923691ef260ed8b1ff11bf3f33c.tar.xz
frr-42d4b30e00131923691ef260ed8b1ff11bf3f33c.zip
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_vrf.h')
-rw-r--r--zebra/zebra_vrf.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/zebra/zebra_vrf.h b/zebra/zebra_vrf.h
index f32f09850..27342908c 100644
--- a/zebra/zebra_vrf.h
+++ b/zebra/zebra_vrf.h
@@ -177,6 +177,8 @@ struct zebra_vrf {
uint64_t lsp_installs;
uint64_t lsp_removals;
+ struct table_manager *tbl_mgr;
+
#if defined(HAVE_RTADV)
struct rtadv rtadv;
#endif /* HAVE_RTADV */