bgpd: add 'mpls bgp forwarding' to ease mpls vpn ebgp peering

RFC4364 describes peerings between multiple AS domains, to ease
the continuity of VPN services across multiple SPs. This commit
implements a sub-set of IETF option b) described in chapter 10 b.

The ASBR to ASBR approach is taken, with an EBGP peering between
the two routers. The EBGP peering must be directly connected to
the outgoing interface used. In those conditions, the next hop
is directly connected, and there is no need to have a transport
label to convey the VPN label. A new vty command is added on a
per interface basis:

This command if enabled, will permit to convey BGP VPN labels
without any transport labels (i.e. with implicit-null label).

restriction:
this command is used only for EBGP directly connected peerings.
Other use cases are not covered.

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

1 files changed, 2 insertions, 0 deletions

diff --git a/bgpd/bgp_main.c b/bgpd/bgp_main.c
index 1297eb440..90ae580ba 100644
--- a/bgpd/bgp_main.c
+++ b/bgpd/bgp_main.c
@@ -511,6 +511,8 @@ int main(int argc, char **argv)
 				 ", bgp@%s:%d", address, bm->port);
 	}
 
+	bgp_if_init();
+
 	frr_config_fork();
 	/* must be called after fork() */
 	bgp_gr_apply_running_config();