summaryrefslogtreecommitdiffstats
path: root/lib/vxlan.h
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@cumulusnetworks.com>2018-10-05 00:42:57 +0200
committerDonald Sharp <sharpd@cumulusnetworks.com>2018-10-12 02:22:19 +0200
commitfbac9605a798444d5845d8dfa179ccb92f33fc0f (patch)
tree7873bc8bf5b56db15ee29655fe0c2b7129ff3c04 /lib/vxlan.h
parentMerge pull request #3140 from vishaldhingra/b_2802 (diff)
downloadfrr-fbac9605a798444d5845d8dfa179ccb92f33fc0f.tar.xz
frr-fbac9605a798444d5845d8dfa179ccb92f33fc0f.zip
lib, zebra: Allow the specification of BUM flooding
Allow the modification of whether or not we will allow BUM flooding on the vxlan bridge. To do this allow the upper level protocol to specify via the ZEBRA_VXLAN_FLOOD_CONTROL zapi message. If flooding is disabled then BUM traffic will not be forwarded to other VTEP's. Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com> Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'lib/vxlan.h')
-rw-r--r--lib/vxlan.h9
1 files changed, 9 insertions, 0 deletions
diff --git a/lib/vxlan.h b/lib/vxlan.h
index ba3dbb05c..bcf835453 100644
--- a/lib/vxlan.h
+++ b/lib/vxlan.h
@@ -26,4 +26,13 @@
typedef uint32_t vni_t;
#define VNI_MAX 16777215 /* (2^24 - 1) */
+/* Flooding mechanisms for BUM packets. */
+/* Currently supported mechanisms are head-end (ingress) replication
+ * (which is the default) and no flooding. Future options could be
+ * using PIM-SM, PIM-Bidir etc.
+ */
+enum vxlan_flood_control {
+ VXLAN_FLOOD_HEAD_END_REPL = 0,
+ VXLAN_FLOOD_DISABLED,
+};
#endif /* __VXLAN_H__ */