From: Andriy Berestovskyy <aber@semihalf.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: ankit bhardwaj <ankitbhrdwj27@gmail.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] How to generate IPSec-based traffic in pktgen ?
Date: Thu, 4 May 2017 09:44:09 +0200 [thread overview]
Message-ID: <CAOysbxreRJ5xQbEZgA19kGjHwnJ88S3ZQCvvh9v_D5a=BOQ2MQ@mail.gmail.com> (raw)
In-Reply-To: <DA1FC280-467A-4A99-9CD4-2C9CC55FE770@intel.com>
Hey,
We used pktgen to generate IPsec traffic using PCAP files. First
configure kernel to encrypt packets with a mode of your choice and
capture the packet with tcpdump. Then just pass the packet to pktgen
with -s option.
Sure it depends on your application, but it might suit the purpose...
Andriy
On Tue, May 2, 2017 at 10:26 PM, Wiles, Keith <keith.wiles@intel.com> wrote:
>
>> On May 2, 2017, at 3:24 AM, ankit bhardwaj <ankitbhrdwj27@gmail.com> wrote:
>>
>> Hi,
>>
>> I want to test IPSec-based application in DPDK and pktgen is the right
>> choice for the packet generation. I could figure out how to generate GRE
>> packets, however, there is no proper documentation for generating
>> IPSec-based packets.
>>
>> Is it possible to generate IPSec-based(ESP/AH) traffic in pktgen, if yes,
>> could you please tell me how to do that?
>
> At this time Pktgen does not support IPSec packets. The only way to use Pktgen and test a IPSec unit is to have PKtgen generate clear text packets and use two IPSec systems to receive clear text convert to IPSec Packets to another machine the convert IPSec to clear text back to Pktgen. I hope that is clear.
>
>>
>> Thanks,
>> Ankit Bhardwaj
>
> Regards,
> Keith
>
--
Andriy Berestovskyy
prev parent reply other threads:[~2017-05-04 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 7:24 ankit bhardwaj
2017-05-02 20:26 ` Wiles, Keith
2017-05-04 7:44 ` Andriy Berestovskyy [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='CAOysbxreRJ5xQbEZgA19kGjHwnJ88S3ZQCvvh9v_D5a=BOQ2MQ@mail.gmail.com' \
--to=aber@semihalf.com \
--cc=ankitbhrdwj27@gmail.com \
--cc=keith.wiles@intel.com \
--cc=users@dpdk.org \
/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).