From: David Miller <davem@davemloft.net>
To: fan.du@windriver.com
Cc: steffen.klassert@secunet.com, netdev@vger.kernel.org
Subject: Re: [PATCHv2 net] {pktgen, xfrm} Update IPv4 header total len and checksum after tranformation
Date: Sun, 01 Dec 2013 20:35:17 -0500 (EST) [thread overview]
Message-ID: <20131201.203517.997917100259265918.davem@davemloft.net> (raw)
In-Reply-To: <1385886528-9882-1-git-send-email-fan.du@windriver.com>
From: Fan Du <fan.du@windriver.com>
Date: Sun, 1 Dec 2013 16:28:48 +0800
> commit a553e4a6317b2cfc7659542c10fe43184ffe53da ("[PKTGEN]: IPSEC support")
> tried to support IPsec ESP transport transformation for pktgen, but acctually
> this doesn't work at all for two reasons(The orignal transformed packet has
> bad IPv4 checksum value, as well as wrong auth value, reported by wireshark)
>
> - After transpormation, IPv4 header total length needs update,
> because encrypted payload's length is NOT same as that of plain text.
>
> - After transformation, IPv4 checksum needs re-caculate because of payload
> has been changed.
>
> With this patch, armmed pktgen with below cofiguration, Wireshark is able to
> decrypted ESP packet generated by pktgen without any IPv4 checksum error or
> auth value error.
>
> pgset "flag IPSEC"
> pgset "flows 1"
>
> Signed-off-by: Fan Du <fan.du@windriver.com>
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2013-12-02 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 8:28 [PATCHv2 net] {pktgen, xfrm} Update IPv4 header total len and checksum after tranformation Fan Du
2013-12-02 1:35 ` David Miller [this message]
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=20131201.203517.997917100259265918.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fan.du@windriver.com \
--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).