From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v8 1/2] examples/ipsec-secgw: add configuration file support
Date: Fri, 23 Sep 2016 22:51:24 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C9FD102@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <76d51670-36b0-ebe1-aefa-7d831a903bf3@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sergio Gonzalez
> Monroy
> Sent: Friday, September 23, 2016 12:53 AM
> To: Zhang, Roy Fan; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v8 1/2] examples/ipsec-secgw: add
> configuration file support
>
> On 21/09/2016 13:05, Fan Zhang wrote:
> > This patch adds the configuration file support to ipsec_secgw
> > sample application. Instead of hard-coded rules, the users can
> > specify their own SP, SA, and routing rules in the configuration
> > file. An command line option "-f" is added to pass the
> > configuration file location to the application.
> >
> > Configuration item formats:
> >
> > SP rule format:
> > sp <ip_ver> <dir> esp <action> <priority> <src_ip> <dst_ip> \
> > <proto> <sport> <dport>
> >
> > SA rule format:
> > sa <dir> <spi> <cipher_algo> <cipher_key> <auth_algo> <auth_key> \
> > <mode> <src_ip> <dst_ip>
> >
> > Routing rule format:
> > rt <ip_ver> <src_ip> <dst_ip> <port>
> >
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> > ---
> > doc/guides/rel_notes/release_16_11.rst | 4 +
> > doc/guides/sample_app_ug/ipsec_secgw.rst | 845 +++++++++++++-----------
> -------
> > examples/ipsec-secgw/Makefile | 1 +
> > examples/ipsec-secgw/ipsec-secgw.c | 58 ++-
> > examples/ipsec-secgw/ipsec.h | 14 +-
> > examples/ipsec-secgw/parser.c | 599 ++++++++++++++++++++++
> > examples/ipsec-secgw/parser.h | 116 +++++
> > examples/ipsec-secgw/rt.c | 255 ++++------
> > examples/ipsec-secgw/sa.c | 747 +++++++++++++++++----------
> > examples/ipsec-secgw/sp4.c | 538 ++++++++++++--------
> > examples/ipsec-secgw/sp6.c | 539 +++++++++++++-------
> > 11 files changed, 2397 insertions(+), 1319 deletions(-)
> > create mode 100644 examples/ipsec-secgw/parser.c
> > create mode 100644 examples/ipsec-secgw/parser.h
>
> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Applied to dpdk-next-crypto, moving the update in release_16_11.rst
from "Resolved issues" to "New Features" section.
Thanks,
Pablo
next prev parent reply other threads:[~2016-09-23 22:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 11:31 [dpdk-dev] [PATCH 0/2] examples/ipsec_secgw: " Fan Zhang
2016-07-07 11:31 ` [dpdk-dev] [PATCH 1/2] " Fan Zhang
2016-07-07 11:31 ` [dpdk-dev] [PATCH 2/2] examples/ipsec-secgw: add sample configuration files Fan Zhang
2016-07-11 14:43 ` [dpdk-dev] [PATCH v2 0/2] examples/ipsec_secgw: add configuration file support Fan Zhang
2016-07-11 14:43 ` [dpdk-dev] [PATCH v2 1/2] examples/ipsec-secgw: " Fan Zhang
2016-07-11 15:19 ` Thomas Monjalon
2016-07-11 14:43 ` [dpdk-dev] [PATCH v2 2/2] examples/ipsec-secgw: add sample configuration files Fan Zhang
2016-07-12 9:44 ` [dpdk-dev] [PATCH v3 0/2] examples/ipsec_secgw: add configuration file support Fan Zhang
2016-07-12 9:44 ` [dpdk-dev] [PATCH v3 1/2] examples/ipsec-secgw: " Fan Zhang
2016-07-19 8:19 ` Sergio Gonzalez Monroy
2016-07-12 9:44 ` [dpdk-dev] [PATCH v3 2/2] examples/ipsec-secgw: add sample configuration files Fan Zhang
2016-07-21 10:51 ` [dpdk-dev] [PATCH v4 0/2] examples/ipsec_secgw: add configuration file support Fan Zhang
2016-07-21 10:51 ` [dpdk-dev] [PATCH v4 1/2] examples/ipsec-secgw: " Fan Zhang
2016-07-21 10:51 ` [dpdk-dev] [PATCH v4 2/2] examples/ipsec-secgw: add sample configuration files Fan Zhang
2016-08-22 10:49 ` [dpdk-dev] [PATCH 0/2] examples/ipsec_secgw: add configuration file support Fan Zhang
2016-08-22 10:49 ` [dpdk-dev] [PATCH 1/2] examples/ipsec-secgw: " Fan Zhang
2016-08-22 10:49 ` [dpdk-dev] [PATCH 2/2] examples/ipsec-secgw: add sample configuration files Fan Zhang
2016-08-23 14:46 ` [dpdk-dev] [PATCH v6 0/2] [PATCH 0/2] examples/ipsec_secgw: add configuration file support Fan Zhang
2016-08-23 14:46 ` [dpdk-dev] [PATCH v6 1/2] examples/ipsec-secgw: " Fan Zhang
2016-09-07 18:13 ` De Lara Guarch, Pablo
2016-08-23 14:46 ` [dpdk-dev] [PATCH v6 2/2] examples/ipsec-secgw: add sample configuration files Fan Zhang
2016-09-20 11:13 ` [dpdk-dev] [PATCH v7 0/2] examples/ipsec_secgw: add configuration file support Fan Zhang
2016-09-20 11:13 ` [dpdk-dev] [PATCH v7 1/2] examples/ipsec-secgw: " Fan Zhang
2016-09-20 11:13 ` [dpdk-dev] [PATCH v7 2/2] examples/ipsec-secgw: add sample configuration files Fan Zhang
2016-09-21 12:05 ` [dpdk-dev] [PATCH v8 0/2] examples/ipsec_secgw: add configuration file support Fan Zhang
2016-09-21 12:05 ` [dpdk-dev] [PATCH v8 1/2] examples/ipsec-secgw: " Fan Zhang
2016-09-23 7:52 ` Sergio Gonzalez Monroy
2016-09-23 22:51 ` De Lara Guarch, Pablo [this message]
2016-09-29 1:19 ` Chen, Zhaoyan
2016-09-21 12:05 ` [dpdk-dev] [PATCH v8 2/2] examples/ipsec-secgw: add sample configuration files Fan Zhang
2016-09-23 7:53 ` Sergio Gonzalez Monroy
2016-09-23 22:51 ` De Lara Guarch, Pablo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E115CCD9D858EF4F90C690B0DCB4D8973C9FD102@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@intel.com \
--cc=sergio.gonzalez.monroy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).