From: Geanta Neag Horia Ioan-B05471 Subject: iproute2 - IPsec ESN support Date: Wed, 25 Jul 2012 06:14:52 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Cc: Stephen Hemminger , Steffen Klassert To: "netdev@vger.kernel.org" , "linux-crypto@vger.kernel.org" Return-path: Received: from va3ehsobe004.messaging.microsoft.com ([216.32.180.14]:2212 "EHLO va3outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750792Ab2GYGO5 convert rfc822-to-8bit (ORCPT ); Wed, 25 Jul 2012 02:14:57 -0400 Content-Language: en-US Sender: linux-crypto-owner@vger.kernel.org List-ID: Hello, Is there any way to create an IPsec tunnel and indicate using extended sequnce numbers? It seems that currently iproute2 doesn't support this. Grepping for "esn" reveals that XFRM_STATE_ESN shows only in kernel headers. The only relevant thing I found was a RFC sent by Steffen (Cc-ed), but it was never applied (don't know why): [RFC] iproute2: Add IPsec extended sequence number support http://patchwork.ozlabs.org/patch/85962/ Thank you, Horia