Add initial code

The inital code is from this patch:
https://gerrit.fd.io/r/#/c/vpp/+/16580/
It is contributed by Intel and Travelping.
Jerome Tollet, Ed Warnicke, Dave Barach, Damjan Marion from Cisco
and other guys have gave lots of useful comments on it.

The initial code is used for identifying layer-7 applications for HTTPS/TLS traffic

- Below is the brief design info.

- Provides a default APPID database for scan.

- Dynamically create new SW mapping has been supported now.

- Support TCP connection state tracking.

- Support TCP segments reassembly on the fly, which handles out-of-order tcp segments and overlapping segments.
  It means that we do not need to reassembly segments first, then dedect applicaion,
  and then fragment segments again, which helps to improve performance.

- Support Hyperscan Stream mode, which can scan rules straddling into different tcp segments.
  It means that if there is a rule "abcde", then "abc" can be in packet 1,
  and "de" can be in packet 2.

- Configure static dpi flows with 5-tuple and VRF-aware, and supports both ipv4 and ipv6 flows.
  These flows will first try to HW offload to NIC based on DPDK rte_flow mechanism
  and vpp/vnet/flow infrastructure.
  If failed, then will create static SW flow mappings.
  Each flow configuration will create two HW or SW flow mappings, i.e. for forward and reverse traffic.
  And both flow mappings will be mapped to the same dpi flow.
  SW entry aging out mechanism will be added later.
        "dpi flow [add | del]  "
        "[src-ip <ip-addr>] [dst-ip <ip-addr>] "
        "[src-port <port>] [dst-port <port>] "
        "[protocol <protocol>] [vrf-id <nn>]",
        "dpi set flow-offload hw <interface-name> rx <flow-id> [del]",
        "dpi set ip4 flow-bypass <interface> [del]",

- When HW flow offload matched, packets will be redirected to DPI plugin with dpi flow_id in packet descriptor.
   If not, packets will be bypassed to DPI plugin from ip-input, and then lookup SW flow mapping table.

- Then will detect layer 7 applications.
   This first patch only detect sub protocls within SSL/TLS.
   1). Identify SSL/TLS certificate message and subsequent segments.
   2). Scan SSL/TLS certificate message through hyperscan, and get application id if matched.
   3). If maximum packets for this flow are checked and not found matched application, the detection will end up.

Ticket:
Type: feature

Signed-off-by: Hongjun Ni <hongjun.ni@intel.com>
Signed-off-by: Andreas Schultz <andreas.schultz@travelping.com>
Signed-off-by: Mathias Gumz <mathias.gumz@travelping.com>
Change-Id: I839cc70ddc80ea594d22a04e2cabf92a7b9c74e7

0 files changed, 0 insertions, 0 deletions