* Re: [dpdk-stable] [dpdk-dev] [PATCH] examples/ipsec-secgw: fix incorrect IPv4 checksum at TX
[not found] ` <d7a225e2-03ed-e193-38ff-b00193b6f76f@intel.com>
@ 2018-07-13 14:41 ` De Lara Guarch, Pablo
0 siblings, 0 replies; only message in thread
From: De Lara Guarch, Pablo @ 2018-07-13 14:41 UTC (permalink / raw)
To: Nicolau, Radu, Ananyev, Konstantin, dev; +Cc: stable
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Radu Nicolau
> Sent: Wednesday, June 6, 2018 2:33 PM
> To: Ananyev, Konstantin <konstantin.ananyev@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: fix incorrect IPv4
> checksum at TX
>
>
> On 6/6/2018 1:04 PM, Konstantin Ananyev wrote:
> > For ESP transport and BYPASS mode the app might generate output
> > packets with invalid IPv4 header checksum.
> > At least such behavior was observed on few Intel NICs.
> > The reason is that the app didn't set ipv4 header checksum to zero
> > before passing it to the HW.
> >
> > Fixes: 906257e965b7 ("examples/ipsec-secgw: support IPv6")
> >
> > Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> > ---
> >
> Acked-by: Radu Nicolau <radu.nicolau@intel.com>
> <mailto:radu.nicolau@intel.com>
Added Cc: stable@dpdk.org
Applied to dpdk-next-crypto.
Thanks,
Pablo
^ permalink raw reply [flat|nested] only message in thread