From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 2B2CD3237 for ; Mon, 18 Jul 2016 16:00:37 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga102.fm.intel.com with ESMTP; 18 Jul 2016 07:00:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,384,1464678000"; d="scan'208";a="997469414" Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.221.12]) ([10.237.221.12]) by orsmga001.jf.intel.com with ESMTP; 18 Jul 2016 07:00:35 -0700 To: Akhil Goyal , "dev@dpdk.org" References: <61dc3eb1-2522-78f5-871d-442d473ab69d@intel.com> From: Sergio Gonzalez Monroy Message-ID: Date: Mon, 18 Jul 2016 15:00:34 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] ip_chksum not updated in ipsec-secgw application X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2016 14:00:37 -0000 On 18/07/2016 14:49, Akhil Goyal wrote: > On 7/18/2016 6:27 PM, Sergio Gonzalez Monroy wrote: >> Hi, >> >> On 18/07/2016 13:41, Akhil Goyal wrote: >>> Hi, >>> >>> In Ipsec-secgw application, while adding the outer IP header, it seems >>> that the application does not update the checksum value for outbound >>> packets. This result in incorrect ip->checksum in the encrypted packet. >>> >>> Please let me know if the checksum value is updated somewhere else or >>> not. >>> >>> Also In case of inner ip header also the TTL value is decremented by >>> one but the checksum value is not updated. Is it intentional or it is >>> done somewhere else? >> >> It is intentional. The application is using IP checksum offload but just >> looking now at the code there is a bug for IPv6 packets where the flag >> does not get setup. >> Is it only for IPv6 traffic that you are having this issue? >> Duh! moment here. No checksum for IPv6, that's why the flag is not setup so the code is correct as it is, it just needs IPv4 checksum offload support. Sergio >> For IPv4 traffic the PKT_TX_IP_CKSUM flag is setup in 'prepare_tx_pkt' >> function in ipsec-secgw.c >> >> Sergio >> > > Thanks Sergio, got your point. I missed the flag. I was using it for > IPv4. > > Akhil > >