DPDK usage discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Avi Cohen (A)" <avi.cohen@huawei.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] l2fwd-crypto sample application
Date: Mon, 22 Jan 2018 09:19:45 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC76854@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <B84047ECBD981D4B93EAE5A6245AA361015956EA@FRAEML521-MBX.china.huawei.com>

Hi Avi,

> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Avi Cohen (A)
> Sent: Sunday, January 21, 2018 4:36 PM
> To: users@dpdk.org
> Subject: [dpdk-users] l2fwd-crypto sample application
> 
> Hi
> Is it possible to run this application for the following use-case:
> 
> [similar to ipsec-secgw application]
> 
> 2 hosts  A and B connected back to back via port 2
> 
> In A:
> -  Clear-text  packet received on port 1
> - Packet is encrypted and sent  to port 2
> 
> In B:
> - the encrypted packet is received on port 2 in server B
> - packet is decrypted and sent to port 1

Yes, the idea would be running L2fwd-crypto on both hosts and both ports.
The command line on host A would be (example: AES-CBC only encryption) :

./l2fwd-crypto -l 1 -n 4 --vdev crypto_X -- --chain CIPHER_ONLY --cipher_algo aes-cbc --cipher_op ENCRYPT /
--cipher_iv_random_size 16 --cipher_key_random_size 16

Whereas, on host B:

./l2fwd-crypto -l 1 -n 4 --vdev crypto_X -- --chain CIPHER_ONLY --cipher_algo aes-cbc --cipher_op DECRYPT /
--cipher_iv_random_size 16 --cipher_key_random_size 16

Pablo

> 
> Best Regards
> Avi
> 

      reply	other threads:[~2018-01-22  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21 16:36 Avi Cohen (A)
2018-01-22  9:19 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8976CC76854@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=avi.cohen@huawei.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).