From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 239] ipsec-secgw fails to initialize when librte_ipsec is enabled
Date: Fri, 05 Apr 2019 08:46:41 +0000 [thread overview]
Message-ID: <bug-239-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190405084641.14dpVQoZ3dk95uIf32q392dQ814e-sqp81tvZCpO0UY@z> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=239
Bug ID: 239
Summary: ipsec-secgw fails to initialize when librte_ipsec is
enabled
Product: DPDK
Version: unspecified
Hardware: ARM
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: lbartosik@marvell.com
Target Milestone: ---
Created attachment 33
--> https://bugs.dpdk.org/attachment.cgi?id=33&action=edit
ipsec_secgw_failure_log.txt
repo http://dpdk.org/git/next/dpdk-next-crypto
branch master
commit 3331ddc doc: update ipsec lib for supported algos
Ipsec-secgw example fails to initialize when librte_ipsec is enabled and when
default configuration of ep0.cfg is used.
It complains that two SP rules use the same SPI
./ipsec-secgw --log-level=8 -c 0xff -- -P -p 0x3 -u 0x1 --config
"(1,0,0),(0,0,0)" -f ../ep0.cfg -l
IPSEC: get_spi_proto: SPI 110 used simultaeously by IPv4(2) and IPv6 (2) SP
rules
EAL: Error - exiting with code: 1
Cause: failed to init inbound SAs
Ipsec-secgw initializes successfully when used without librte_ipsec.
Full log is attached.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-04-05 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 8:46 bugzilla [this message]
2019-04-05 8:46 ` bugzilla
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=bug-239-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).