From: Peng Zhang <peng1x.zhang@intel.com>
To: dts@dpdk.org
Cc: Peng Zhang <peng1x.zhang@intel.com>
Subject: [dts][PATCH V1] Modify ipsec configuration of script
Date: Sat, 2 Apr 2022 18:31:53 +0800 [thread overview]
Message-ID: <20220402103153.2305190-1-peng1x.zhang@intel.com> (raw)
Modify ipsec configuration of script because of commit id which is a15f7b7d8aac9cca41d8bd022c3cf939a6a8d2e8 will lead to dts test case fail.
Signed-off-by: Peng Zhang <peng1x.zhang@intel.com>
---
tests/TestSuite_inline_ipsec.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/TestSuite_inline_ipsec.py b/tests/TestSuite_inline_ipsec.py
index 5d8332a4..5fceda98 100644
--- a/tests/TestSuite_inline_ipsec.py
+++ b/tests/TestSuite_inline_ipsec.py
@@ -113,6 +113,7 @@ class TestInlineIpsec(TestCase):
"sp ipv4 out esp protect 1005 pri 1 dst 192.168.105.0/24 sport 0:65535 dport 0:65535\n"
"#SA rules\n"
"sa out 1005 aead_algo aes-128-gcm aead_key 2b:7e:15:16:28:ae:d2:a6:ab:f7:15:88:09:cf:4f:3d:de:ad:be:ef mode ipv4-tunnel src 172.16.1.5 dst 172.16.2.5 port_id 1 type inline-crypto-offload\n"
+ "sa in 5 aead_algo aes-128-gcm aead_key 2b:7e:15:16:28:ae:d2:a6:ab:f7:15:88:09:cf:4f:3d:de:ad:be:ef mode ipv4-tunnel src 172.16.2.5 dst 172.16.1.5 port_id 1 type inline-crypto-offload"
"#Routing rules\n"
"rt ipv4 dst 172.16.2.5/32 port 1\n")
@@ -126,6 +127,7 @@ class TestInlineIpsec(TestCase):
"#SP IPv4 rules\n"
"sp ipv4 out esp protect 1002 pri 1 dst 192.168.102.0/24 sport 0:65535 dport 0:65535\n"
"sa out 1002 aead_algo aes-128-gcm aead_key 2b:7e:15:16:28:ae:d2:a6:ab:f7:15:88:09:cf:4f:3d:de:ad:be:ef mode ipv4-tunnel src 172.16.31.35 dst 172.16.32.35 port_id 1 type inline-crypto-offload \n"
+ "sa in 5 aead_algo aes-128-gcm aead_key 2b:7e:15:16:28:ae:d2:a6:ab:f7:15:88:09:cf:4f:3d:de:ad:be:ef mode ipv4-tunnel src 172.16.32.35 dst 172.16.31.35 port_id 1 type inline-crypto-offload"
"#Routing rules\n"
"rt ipv4 dst 172.16.32.35/32 port 1\n"
)
--
2.31.1
reply other threads:[~2022-04-01 7:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220402103153.2305190-1-peng1x.zhang@intel.com \
--to=peng1x.zhang@intel.com \
--cc=dts@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).