Re: [dpdk-dev] [PATCH v2] examples/ipsec-secgw: fix SPD no-match is misinterpreted

2019-04-23 Thread Akhil Goyal
> -Original Message- > From: Zhang, Roy Fan > Sent: Friday, April 5, 2019 12:10 AM > To: Ananyev, Konstantin ; dev@dpdk.org > Cc: Akhil Goyal ; Ananyev, Konstantin > ; sta...@dpdk.org > Subject: RE: [dpdk-dev] [PATCH v2] examples/ipsec-secgw: fix SPD no-matc

Re: [dpdk-dev] [PATCH v2] examples/ipsec-secgw: fix SPD no-match is misinterpreted

2019-04-04 Thread Zhang, Roy Fan
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Konstantin > Ananyev > Sent: Thursday, April 4, 2019 1:13 PM > To: dev@dpdk.org > Cc: akhil.go...@nxp.com; Ananyev, Konstantin > ; sta...@dpdk.org > Subject: [dpdk-dev] [PATCH v2] examp

[dpdk-dev] [PATCH v2] examples/ipsec-secgw: fix SPD no-match is misinterpreted

2019-04-04 Thread Konstantin Ananyev
acl_classify() returns zero value when no matching rule was found. Currently ipsec-secgw treats it as a valid SPI value, though it has to discard such packets. Error could be easily observed by sending outbound unmatched packets, user will see something like that in the log: IPSEC: No cryptodev: co