zebra: importation of bgp evpn rt5 from vni with other netns

With vrf-lite mechanisms, it is possible to create layer 3 vnis by
creating a bridge interface in default vr, by creating a vxlan interface
that is attached to that bridge interface, then by moving the vxlan
interface to the wished vrf.
With vrf-netns mechanism, it is slightly different since bridged
interfaces can not be separated in different network namespaces. To make
it work, the setup consists in :
- creating a vxlan interface on default vrf.
- move the vxlan interface to the wished vrf ( with an other netns)
- create a bridge interface in the wished vrf
- attach the vxlan interface to that bridged interface

from that point, if BGP is enabled to advertise vnis in default vrf,
then vxlan interfaces are discovered appropriately in other vrfs,
provided that the link interface still resides in the vrf where l2vpn is
advertised.
to import ipv4 entries from a separate vrf, into the l2vpn, the
configuration of vni in the dedicated vrf + the advertisement of ipv4
entries in bgp vrf will import the entries in the bgp l2vpn.

the modification consists in parsing the vxlan interfaces in all network
namespaces, where the link resides in the same network namespace as the
bgp core instance where bgp l2vpn is enabled.

Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>

1 files changed, 8 insertions, 0 deletions

diff --git a/zebra/zebra_ns.h b/zebra/zebra_ns.h
index dc79a83db..fa2fd47c2 100644
--- a/zebra/zebra_ns.h
+++ b/zebra/zebra_ns.h
@@ -72,6 +72,14 @@ int zebra_ns_final_shutdown(struct ns *ns);
 
 int zebra_ns_config_write(struct vty *vty, struct ns *ns);
 
+#define ZNS_WALK_CONTINUE 0
+#define ZNS_WALK_STOP 1
+void zebra_ns_list_walk(int (*exec_for_each_zns)(struct zebra_ns *zns,
+						 void *param_in,
+						 void **param_out),
+			void *param_in,
+			void **param_out);
+
 #ifdef __cplusplus
 }
 #endif