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

Hi Akhil, > > > > 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 som

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

> Hi Akhil, > > > > > On 3/28/2019 6:17 PM, Konstantin Ananyev wrote: > > > 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 o

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

Hi Akhil, > > On 3/28/2019 6:17 PM, Konstantin Ananyev wrote: > > 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 unmatche

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

Hi Konstantin, On 3/28/2019 6:17 PM, Konstantin Ananyev wrote: > 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 packet

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

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