DPDK-dev Archive on lore.kernel.org
 help / color / Atom feed
From: Anoob Joseph <anoobj@marvell.com>
To: Lukas Bartosik <lbartosik@marvell.com>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"radu.nicolau@intel.com" <radu.nicolau@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Lukas Bartosik <lbartosik@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: update default configuration
Date: Sat, 9 Nov 2019 11:26:17 +0000
Message-ID: <MN2PR18MB28778B70DA841D86C59439E6DF7A0@MN2PR18MB2877.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1573055294-32502-1-git-send-email-lbartosik@marvell.com>

@Akhil, do we need this submitted to dpdk-stable?

Acked-by: Anoob Joseph <anoobj@marvell.com>

> -----Original Message-----
> From: Lukasz Bartosik <lbartosik@marvell.com>
> Sent: Wednesday, November 6, 2019 9:18 PM
> To: konstantin.ananyev@intel.com; akhil.goyal@nxp.com;
> radu.nicolau@intel.com
> Cc: dev@dpdk.org; Anoob Joseph <anoobj@marvell.com>; Lukas Bartosik
> <lbartosik@marvell.com>
> Subject: [PATCH] examples/ipsec-secgw: update default configuration
> 
> Update default configuration of ipsec-secgw:
> 1.In ep0.cfg change SPI value used by two inbound IPv6 security policies from 15
> to 115 and 16 to 116 to point to existing inbound SAs. There are no inbound SAs
> with SPI value 15, 16.
> - In ep1.cfg change SPI value used by two outbound IPv6 security policies from
> 15 to 115 and 16 to 116 to point to existing outbound SAs. There are no
> outbound SAs with SPI value 15, 16. Add missing priority parameter in two
> inbound IPv4 security policies.
> 
> Signed-off-by: Lukasz Bartosik <lbartosik@marvell.com>
> ---
>  examples/ipsec-secgw/ep0.cfg |  8 ++++----  examples/ipsec-secgw/ep1.cfg |
> 12 ++++++------
>  2 files changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/examples/ipsec-secgw/ep0.cfg b/examples/ipsec-secgw/ep0.cfg
> index 299aa9e..dfd4aca 100644
> --- a/examples/ipsec-secgw/ep0.cfg
> +++ b/examples/ipsec-secgw/ep0.cfg
> @@ -49,14 +49,14 @@ sport 0:65535 dport 0:65535  sp ipv6 out esp protect 26
> pri 1 dst 0000:0000:0000:0000:bbbb:bbbb:0000:0000/96 \  sport 0:65535 dport
> 0:65535
> 
> -sp ipv6 in esp protect 15 pri 1 dst ffff:0000:0000:0000:5555:5555:0000:0000/96
> \ -sport 0:65535 dport 0:65535 -sp ipv6 in esp protect 16 pri 1 dst
> ffff:0000:0000:0000:6666:6666:0000:0000/96 \ -sport 0:65535 dport 0:65535
> sp ipv6 in esp protect 110 pri 1 dst ffff:0000:1111:1111:0000:0000:0000:0000/96
> \  sport 0:65535 dport 0:65535  sp ipv6 in esp protect 111 pri 1 dst
> ffff:0000:1111:1111:1111:1111:0000:0000/96 \  sport 0:65535 dport 0:65535
> +sp ipv6 in esp protect 115 pri 1 dst
> +ffff:0000:0000:0000:5555:5555:0000:0000/96 \ sport 0:65535 dport
> +0:65535 sp ipv6 in esp protect 116 pri 1 dst
> +ffff:0000:0000:0000:6666:6666:0000:0000/96 \ sport 0:65535 dport
> +0:65535
>  sp ipv6 in esp protect 125 pri 1 dst
> ffff:0000:0000:0000:aaaa:aaaa:0000:0000/96 \  sport 0:65535 dport 0:65535  sp
> ipv6 in esp protect 126 pri 1 dst ffff:0000:0000:0000:bbbb:bbbb:0000:0000/96 \
> diff --git a/examples/ipsec-secgw/ep1.cfg b/examples/ipsec-secgw/ep1.cfg
> index 3f6ff81..19bdc68 100644
> --- a/examples/ipsec-secgw/ep1.cfg
> +++ b/examples/ipsec-secgw/ep1.cfg
> @@ -19,8 +19,8 @@ sp ipv4 in esp protect 15 pri 1 dst 192.168.200.0/24 sport
> 0:65535 dport 0:65535  sp ipv4 in esp protect 16 pri 1 dst 192.168.201.0/24 sport
> 0:65535 dport 0:65535  sp ipv4 in esp protect 25 pri 1 dst 192.168.55.0/24 sport
> 0:65535 dport 0:65535  sp ipv4 in esp protect 26 pri 1 dst 192.168.56.0/24 sport
> 0:65535 dport 0:65535 -sp ipv4 in esp bypass dst 192.168.240.0/24 sport
> 0:65535 dport 0:65535 -sp ipv4 in esp bypass dst 192.168.241.0/24 sport
> 0:65535 dport 0:65535
> +sp ipv4 in esp bypass pri 1 dst 192.168.240.0/24 sport 0:65535 dport
> +0:65535 sp ipv4 in esp bypass pri 1 dst 192.168.241.0/24 sport 0:65535
> +dport 0:65535
> 
>  sp ipv4 out esp protect 105 pri 1 dst 192.168.115.0/24 sport 0:65535 dport
> 0:65535  sp ipv4 out esp protect 106 pri 1 dst 192.168.116.0/24 sport 0:65535
> dport 0:65535 @@ -49,14 +49,14 @@ sport 0:65535 dport 0:65535  sp ipv6 in
> esp protect 26 pri 1 dst 0000:0000:0000:0000:bbbb:bbbb:0000:0000/96 \  sport
> 0:65535 dport 0:65535
> 
> -sp ipv6 out esp protect 15 pri 1 dst
> ffff:0000:0000:0000:5555:5555:0000:0000/96 \ -sport 0:65535 dport 0:65535 -
> sp ipv6 out esp protect 16 pri 1 dst
> ffff:0000:0000:0000:6666:6666:0000:0000/96 \ -sport 0:65535 dport 0:65535
> sp ipv6 out esp protect 110 pri 1 dst
> ffff:0000:1111:1111:0000:0000:0000:0000/96 \  sport 0:65535 dport 0:65535  sp
> ipv6 out esp protect 111 pri 1 dst ffff:0000:1111:1111:1111:1111:0000:0000/96
> \  sport 0:65535 dport 0:65535
> +sp ipv6 out esp protect 115 pri 1 dst
> +ffff:0000:0000:0000:5555:5555:0000:0000/96 \ sport 0:65535 dport
> +0:65535 sp ipv6 out esp protect 116 pri 1 dst
> +ffff:0000:0000:0000:6666:6666:0000:0000/96 \ sport 0:65535 dport
> +0:65535
>  sp ipv6 out esp protect 125 pri 1 dst
> ffff:0000:0000:0000:aaaa:aaaa:0000:0000/96 \  sport 0:65535 dport 0:65535  sp
> ipv6 out esp protect 126 pri 1 dst ffff:0000:0000:0000:bbbb:bbbb:0000:0000/96
> \
> --
> 2.7.4


  reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 15:48 Lukasz Bartosik
2019-11-09 11:26 ` Anoob Joseph [this message]
2019-11-18  7:54   ` Akhil Goyal

Reply instructions:

You may reply publically 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=MN2PR18MB28778B70DA841D86C59439E6DF7A0@MN2PR18MB2877.namprd18.prod.outlook.com \
    --to=anoobj@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=lbartosik@marvell.com \
    --cc=radu.nicolau@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

DPDK-dev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \
		dev@dpdk.org
	public-inbox-index dpdk-dev

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git