* [dpdk-dev] [Bug 239] ipsec-secgw fails to initialize when librte_ipsec is enabled
@ 2019-04-05 8:46 bugzilla
2019-04-05 8:46 ` bugzilla
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2019-04-05 8:46 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-04-05 8:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-05 8:46 [dpdk-dev] [Bug 239] ipsec-secgw fails to initialize when librte_ipsec is enabled bugzilla
2019-04-05 8:46 ` bugzilla
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).