DPDK usage discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: Bartlomiej <bartek@conclusive.pl>, users@dpdk.org
Subject: Re: [dpdk-users] Problem with ipsec-secgw on DPAA
Date: Tue, 13 Apr 2021 10:43:13 +0530	[thread overview]
Message-ID: <faf148a0-af9c-4048-f9ae-c4844cab9313@oss.nxp.com> (raw)
In-Reply-To: <8c26ceea-1403-8b3b-98f2-f9cd556cb699@conclusive.pl>

Hi Bartlomiej,

     I hope you are following the LSDK user guide w.r.t using right dtb 
file for userspace mode.


Regards,

Hemant

On 4/12/2021 9:33 PM, Bartlomiej wrote:
> Hello,
>
> I have a couple of problems with the example apps.
>
> The setup used for testing is a custom LS1046A-based board running 
> QorIQ 4.19 linux kernel. DPDK is built from the main branch with the 
> DPAA driver, specifically commit 41e026c1b3fd07ee. One of the ethernet 
> ports is under DPDK control and is plugged in directly into another 
> board for inspection of egress traffic. The DPDK apps are spawned with 
> a tap virtual device to insert some UDP packets for testing.
>
> My goal is to run the ipsec-secgw app on it with hardware encryption.
>
> I managed to run l2fwd successfully, but have a couple of problems 
> with other example apps:
> 1) l2fwd-crypto crashes on `struct qm_portal` access, which after 
> checking in gdb seems to consist of zeros.
> 2) ipsec-secgw - No matter what config I use, the only thing I managed 
> so far is to forward the UDP packets from the tap device to the 
> ethernet port. There is no ESP and the contents are unencrypted on the 
> other device. The config used:
>
> ```
> sp ipv4 in esp protect 5 pri 2 dst 10.0.3.0/24 sport 0:65535 dport 
> 0:65535
>
> sa in 5 \
> cipher_algo aes-128-cbc \
> cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
> auth_algo sha1-hmac \
> auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
> mode ipv4-tunnel \
> src 10.0.3.100 dst 100.0.3.101 \
> port_id 0 type lookaside-protocol-offload
>
> rt ipv4 dst 10.0.3.0/24 port 0
> ```
>
> The UDP packets are generated according to this spec:
> https://gist.github.com/bartlomiejn/2607847a3f70d543da92f5717b88fa4e
>
> Is my config correct? Can anyone help with diagnosing this problem?
>
> Best regards,
> Bartlomiej Nowak
> Software Engineer
> Conclusive Engineering
>

      reply	other threads:[~2021-04-13  5:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 16:03 Bartlomiej
2021-04-13  5:13 ` Hemant Agrawal [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=faf148a0-af9c-4048-f9ae-c4844cab9313@oss.nxp.com \
    --to=hemant.agrawal@oss.nxp.com \
    --cc=bartek@conclusive.pl \
    --cc=hemant.agrawal@nxp.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).