> -----Original Message----- > From: dev [mailto:[email protected]] On Behalf Of Radu Nicolau > Sent: Wednesday, June 6, 2018 2:33 PM > To: Ananyev, Konstantin <[email protected]>; [email protected] > 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 <[email protected]> > > --- > > > Acked-by: Radu Nicolau <[email protected]> > <mailto:[email protected]>
Added Cc: [email protected] Applied to dpdk-next-crypto. Thanks, Pablo
