From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org, konstantin.ananyev@intel.com, akhil.goyal@nxp.com
Cc: Bernard Iremonger <bernard.iremonger@intel.com>, stable@dpdk.org
Subject: [dpdk-stable] [PATCH v3 2/2] examples/ipsec-secgw/test: fix inline test scripts
Date: Thu, 4 Apr 2019 14:28:15 +0100 [thread overview]
Message-ID: <1554384495-7936-3-git-send-email-bernard.iremonger@intel.com> (raw)
In-Reply-To: <1551970666-23557-1-git-send-email-bernard.iremonger@intel.com>
Remove workaround in tun_aesgcm_defs.sh and trs_aesgcm_defs.sh
to get around the bug where the first inbound packet is dropped
for inline crypto.
Fixes: 929784452094 ("examples/ipsec-secgw: add scripts for functional test")
Cc: stable@dpdk.org
Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
examples/ipsec-secgw/test/trs_aesgcm_defs.sh | 10 ----------
examples/ipsec-secgw/test/tun_aesgcm_defs.sh | 10 ----------
2 files changed, 20 deletions(-)
diff --git a/examples/ipsec-secgw/test/trs_aesgcm_defs.sh b/examples/ipsec-secgw/test/trs_aesgcm_defs.sh
index a4d902b..8382d3d 100644
--- a/examples/ipsec-secgw/test/trs_aesgcm_defs.sh
+++ b/examples/ipsec-secgw/test/trs_aesgcm_defs.sh
@@ -33,11 +33,6 @@ aead "rfc4106\(gcm\(aes\)\)" \
ssh ${REMOTE_HOST} ip xfrm policy list
ssh ${REMOTE_HOST} ip xfrm state list
-
- # to overcome problem with ipsec-secgw for inline mode,
- # when first packet(s) will be always dropped.
- # note that ping will fail here
- ssh ${REMOTE_HOST} ping -c 1 ${LOCAL_IPV4}
}
config6_remote_xfrm()
@@ -68,9 +63,4 @@ aead "rfc4106\(gcm\(aes\)\)" \
ssh ${REMOTE_HOST} ip xfrm policy list
ssh ${REMOTE_HOST} ip xfrm state list
-
- # to overcome problem with ipsec-secgw for inline mode,
- # when first packet(s) will be always dropped.
- # note that ping will fail here
- ssh ${REMOTE_HOST} ping -c 1 ${LOCAL_IPV6}
}
diff --git a/examples/ipsec-secgw/test/tun_aesgcm_defs.sh b/examples/ipsec-secgw/test/tun_aesgcm_defs.sh
index 1764ef6..8ae6532 100644
--- a/examples/ipsec-secgw/test/tun_aesgcm_defs.sh
+++ b/examples/ipsec-secgw/test/tun_aesgcm_defs.sh
@@ -35,11 +35,6 @@ aead "rfc4106\(gcm\(aes\)\)" \
ssh ${REMOTE_HOST} ip xfrm policy list
ssh ${REMOTE_HOST} ip xfrm state list
-
- # to overcome problem with ipsec-secgw for inline mode,
- # when first packet(s) will be always dropped.
- # note that ping will fail here
- ssh ${REMOTE_HOST} ping -c 1 ${LOCAL_IPV4}
}
config6_remote_xfrm()
@@ -72,9 +67,4 @@ aead "rfc4106\(gcm\(aes\)\)" \
ssh ${REMOTE_HOST} ip xfrm policy list
ssh ${REMOTE_HOST} ip xfrm state list
-
- # to overcome problem with ipsec-secgw for inline mode,
- # when first packet(s) will be always dropped.
- # note that ping will fail here
- ssh ${REMOTE_HOST} ping6 -c 1 ${LOCAL_IPV6}
}
--
2.7.4
prev parent reply other threads:[~2019-04-04 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1551970666-23557-1-git-send-email-bernard.iremonger@intel.com>
2019-04-04 13:28 ` [dpdk-stable] [PATCH v3 1/2] examples/ipsec-secgw: fix 1st packet dropped for inline crypto Bernard Iremonger
2019-04-17 11:51 ` Akhil Goyal
2019-04-17 12:53 ` Iremonger, Bernard
2019-04-17 13:01 ` [dpdk-stable] [EXT] " Akhil Goyal
2019-04-04 13:28 ` Bernard Iremonger [this message]
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=1554384495-7936-3-git-send-email-bernard.iremonger@intel.com \
--to=bernard.iremonger@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=stable@dpdk.org \
/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).