DPDK patches and discussions
 help / color / mirror / Atom feed
From: satyavalli rama <satyavalli.rama@gmail.com>
To: dev@dpdk.org, users@dpdk.org
Subject: [dpdk-dev] Ipsec-secgw packet processing
Date: Mon, 17 Aug 2020 16:11:33 +0530	[thread overview]
Message-ID: <CAECt3bNPHbsoOEhHDfWbxOTyg4UyE1AJYOm++_V=MgEwAbGHBg@mail.gmail.com> (raw)
In-Reply-To: <CAECt3bPG__2Lz_fLhRtr4oPfWNaSz+-RGvj4N86GbjxSMOa5rA@mail.gmail.com>

Hello,

While we are running ipsec-secgw application in transport-mode on
dpdk-19.02, we found that inline packet processing is not happening.

And also we are not observing any encrypt/decrypt packets on pdump before
sending packets out from tx-port(rte_eth_tx_burst()).

Please help us on how to proceed further.

Thanks,
Jagadeesh

  parent reply	other threads:[~2020-08-17 10:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMJ3rejJ4_7bYrZ1=kAsWds4A53UNBVePNdVCGpr3BDzAWAsSA@mail.gmail.com>
     [not found] ` <CAMJ3rejbOZ5mzOYyNPFqVk-Scs7CTaVZLUQOd-GMnVpaYf+pmg@mail.gmail.com>
2020-01-06  5:55   ` [dpdk-dev] Fwd: l2fwd application are not sending continuous packets satyavalli rama
2020-01-06  7:07     ` [dpdk-dev] " satyavalli rama
2020-01-09  1:55     ` satyavalli rama
2020-01-09  6:12       ` Stephen Hemminger
2020-01-09 10:34         ` satyavalli rama
2020-08-17 10:41     ` satyavalli rama [this message]
2020-08-18 10:37       ` [dpdk-dev] Ipsec-secgw packet processing satyavalli rama
2020-08-18 10:59         ` Anoob Joseph
2020-08-19 11:08           ` satyavalli rama
2020-08-26 11:23             ` satyavalli rama
2020-08-31  5:17               ` [dpdk-dev] [EXT] " Anoob Joseph
2020-08-31 12:47                 ` Pathak, Pravin
2020-09-01 11:07                   ` Iremonger, Bernard
2020-08-28 18:06             ` [dpdk-dev] " satyavalli rama
2020-08-11  8:26 jagadeesh reddy

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='CAECt3bNPHbsoOEhHDfWbxOTyg4UyE1AJYOm++_V=MgEwAbGHBg@mail.gmail.com' \
    --to=satyavalli.rama@gmail.com \
    --cc=dev@dpdk.org \
    --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).