Convert lisp-gpe encap to interface tx node 48/848/2
authorFlorin Coras <fcoras@cisco.com>
Wed, 20 Apr 2016 22:45:40 +0000 (00:45 +0200)
committerDave Barach <openvpp@barachs.net>
Mon, 25 Apr 2016 13:05:49 +0000 (13:05 +0000)
commit577c3553dd6939e998c78c5a389750aac3a67f8b
tree3a95da61f5cfca2d1629a8011d2a6b57ae19bad2
parent405e41b50e336dccfdeeafae93bf4453774ecfec
Convert lisp-gpe encap to interface tx node

With this change, one lisp-gpe interface is created per vrf/overlay
tenant and its tx node is used as encapsulator (or tunnel ingress). For
all intents and purposes, the tx node inherits all functions previously
performed by the lisp-gpe-encap node and it maintains said node's
position in lisp-gpe's data-path graph. Chiefly, this opens the
possibility to chain interface features, like IPSec, transparently with
LISP. Furthermore, it brings basic data plane support for vrfs and LISP
instance-ids (or virtual network instances as per RFC7364).

Other changes include improvements to lisp-gpe enable and disable
sequences and corresponding API/VAT fixes.

Change-Id: I085500450660a976b587b1a720e282f6e728d580
Signed-off-by: Florin Coras <fcoras@cisco.com>
12 files changed:
vnet/Makefile.am
vnet/vnet/lisp-cp/control.c
vnet/vnet/lisp-cp/control.h
vnet/vnet/lisp-gpe/decap.c
vnet/vnet/lisp-gpe/encap.c [deleted file]
vnet/vnet/lisp-gpe/interface.c [new file with mode: 0644]
vnet/vnet/lisp-gpe/lisp_gpe.c
vnet/vnet/lisp-gpe/lisp_gpe.h
vnet/vnet/lisp-gpe/lisp_gpe_error.def
vpp-api-test/vat/api_format.c
vpp/api/api.c
vpp/api/vpe.api