DPDK usage discussions
 help / color / mirror / Atom feed
From: gaurav maheshwari <gmaheshwari24.6@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Facing failure with enabling macsec in 82599EB
Date: Fri, 4 Jan 2019 11:25:18 +0530	[thread overview]
Message-ID: <CAJ+HfNbT2e7z_KfX978tngu_FwWq_7xQFfgSKYvLhMiN+92qbg@mail.gmail.com> (raw)

Hi,

We are try  to enable macsec on Intel nic 82599EB, we are facing failure in
doing so.
While enabling the macsec in testpmd, in rx side we are seeing 4 bytes
missing.
This behavior  is not seen when macsec is disabled.

I am adding below pdump output to show the tx and rx dump.

*TX SIDE:*

./dpdk-pdump    --file-prefix=tx  -w  0000:87:00.0  --      --pdump
'port=0,queue=*,tx-dev=/tmp/capture.pcap'



04:01:47.717972 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto
UDP (17), length 50)

    192.168.0.1.1024 > 192.168.0.2.1024: [no cksum] UDP, length 22

        0x0000:  0200 0000 0000 0090 0b50 955a 0800 4500

        0x0010:  0032 0000 0000 4011 f967 c0a8 0001 c0a8

        0x0020:  0002 0400 0400 001e 0000 0000 0000 0000

        0x0030:  0000 0000 0000 0000 0000 0000 0000 0000



*RX SIDE:*

./dpdk-pdump    --file-prefix=tx  -w  0000:87:00.0  --      --pdump
'port=0,queue=*,rx-dev=/tmp/capture.pcap'



0*6:51:04.734853 IP truncated-ip - 4 bytes missing!* (tos 0x0, ttl 64, id
0, offset 0, flags [none], proto UDP (17), length 50)

    192.168.0.1.1024 > 192.168.0.2.1024: [no cksum] UDP, length 22

        0x0000:  4500 0032 0000 0000 4011 f967 c0a8 0001

        0x0010:  c0a8 0002 0400 0400 001e 0000 0000 0000

        0x0020:  0000 0000 0000 0000 0000 0000 0000



We are following the below configuration
https://doc.dpdk.org/dts/test_plans/macsec_for_ixgbe_test_plan.html

Please let me know if additional data is required.


Regards,
Gaurav

                 reply	other threads:[~2019-01-04  6:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAJ+HfNbT2e7z_KfX978tngu_FwWq_7xQFfgSKYvLhMiN+92qbg@mail.gmail.com \
    --to=gmaheshwari24.6@gmail.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).