From: Fan Du <fan.du@windriver.com>
To: <davem@davemloft.net>
Cc: <steffen.klassert@secunet.com>, <hadi@cyberus.ca>,
<netdev@vger.kernel.org>
Subject: [PATCHv4 net-next 0/8] pktgen IPsec support
Date: Fri, 20 Dec 2013 10:33:26 +0800 [thread overview]
Message-ID: <1387506814-4417-1-git-send-email-fan.du@windriver.com> (raw)
Hi, Dave
Current pktgen IPsec supports only transport/ESP combinnation,
This patchset enables user to do almost any IPsec transformation,
both transport/tunnel mode, and AH/ESP/IPcomp type.
Below configuration has been tested, and using Wireshark could decrypt
out plain text in good formation without any checksum/auth errors:
Mode/TYPE AH ESP
Transport x x
Tunnel x x
ChangeLog
v2:
Rebase patchset against newest net-next.
Patch1: Remove adding rebundant empty line spotted by Sergei.
Patch2: Use only one dst pointing into itself to save space.
v3:
Align with David's requirement, that for user depends on orignal
a553e4a6317b2cfc7659542c10fe43184ffe53da ("IPSEC support") from
Jamal, their testbed configuration will not need to be changed.
Add Patch2/7, Patch3/7 for statistic counting, as well as fixing
lock usage issue.
v4:
Add Patch8/8 to document IPsec usage in pktgen, both for orignal
implementation and this enhancement, adviced by Jamal. And comment
format fix spoted by Sergei.
Fan Du (8):
{pktgen, xfrm} Correct xfrm state lock usage when transforming
{pktgen, xfrm} Add statistics counting when transforming
{pktgen, xfrm} Correct xfrm_state_lock usage in xfrm_stateonly_find
{pktgen, xfrm} Using "pgset spi xxx" to spedifiy SA for a given flow
{pktgen, xfrm} Construct skb dst for tunnel mode transformation
{pktgen, xfrm} Introduce xfrm_state_lookup_byspi for pktgen
{pktgen, xfrm} Show spi value properly when ipsec turned on
{pktgen, xfrm} Document IPsec usage in pktgen.txt
Documentation/networking/pktgen.txt | 15 +++++++
include/net/xfrm.h | 2 +
net/core/pktgen.c | 80 +++++++++++++++++++++++++++++------
net/xfrm/xfrm_state.c | 26 +++++++++++-
4 files changed, 107 insertions(+), 16 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-12-20 2:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 2:33 Fan Du [this message]
2013-12-20 2:33 ` [PATCHv4 net-next 1/8] {pktgen, xfrm} Correct xfrm state lock usage when transforming Fan Du
2013-12-20 2:33 ` [PATCHv4 net-next 2/8] {pktgen, xfrm} Add statistics counting " Fan Du
2013-12-20 2:33 ` [PATCHv4 net-next 3/8] {pktgen, xfrm} Correct xfrm_state_lock usage in xfrm_stateonly_find Fan Du
2014-01-02 7:32 ` Steffen Klassert
2013-12-20 2:33 ` [PATCHv4 net-next 4/8] {pktgen, xfrm} Using "pgset spi xxx" to spedifiy SA for a given flow Fan Du
2013-12-20 2:33 ` [PATCHv4 net-next 5/8] {pktgen, xfrm} Construct skb dst for tunnel mode transformation Fan Du
2013-12-20 2:33 ` [PATCHv4 net-next 6/8] {pktgen, xfrm} Introduce xfrm_state_lookup_byspi for pktgen Fan Du
2013-12-20 2:33 ` [PATCHv4 net-next 7/8] {pktgen, xfrm} Show spi value properly when ipsec turned on Fan Du
2013-12-20 2:33 ` [PATCHv4 net-next 8/8] {pktgen, xfrm} Document IPsec usage in pktgen.txt Fan Du
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1387506814-4417-1-git-send-email-fan.du@windriver.com \
--to=fan.du@windriver.com \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).