examples/ipsec-secgw: support inline protocol
authorAnoob Joseph <anoob.joseph@caviumnetworks.com>
Mon, 18 Dec 2017 07:15:05 +0000 (07:15 +0000)
committerPablo de Lara <pablo.de.lara.guarch@intel.com>
Sat, 20 Jan 2018 15:10:20 +0000 (16:10 +0100)
commit0ccfd14bc10df18c6437afe23761794d9b20e0a1
treea974a229a3c8bf7d753c0c16f7096f7f8ed7755e
parent1a08c379b9b5edeb0214378daa3fb2e56fba49ba
examples/ipsec-secgw: support inline protocol

Adding support for inline protocol processing

In ingress side, application will receive regular IP packets, without
any IPsec related info. Application will do a selector check (SP-SA
check) by making use of the metadata from the packet. The
device-specific metadata in mbuf would aid in determing the security
session which processed the packet.

In egress side, the plain packet would be submitted to the driver. The
packet will have optional metadata, which could be used to identify the
security session associated with the packet.

Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com>
Reviewed-by: Akhil Goyal <akhil.goyal@nxp.com>
examples/ipsec-secgw/esp.c
examples/ipsec-secgw/ipsec-secgw.c
examples/ipsec-secgw/ipsec.c