DPDK patches and discussions
 help / color / mirror / Atom feed
From: sagar g <sagargadher@gmail.com>
To: dev@dpdk.org
Subject: Re: ESP Packet drop issue
Date: Thu, 29 Feb 2024 13:27:33 +0530	[thread overview]
Message-ID: <CAOCi-21qMaFa3KZ8mJCVYV4PZd6jZ-f9NyJ-tOE6qCUTorf-GA@mail.gmail.com> (raw)
In-Reply-To: <CAOCi-21JP-dt6-8SfC_2UKM+jdGqv2N47JHu6grMN2GYSORieQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4771 bytes --]

On Thu, Feb 29, 2024 at 1:26 PM sagar g <sagargadher@gmail.com> wrote:

> Hi All,
>
> We are using dpdk-23.03 (Intel iAVF pci: device 8086:154c) along with
> FDIO23.06 VPP.
>
> In VPP Application we are seeing that ESP Packet is sent out to
> iavf_xmit_pkts() function.
>
> But ESP Packet is not sent out of NIC.
>
> What could be the reasons and how to debug this? Any help would be
> appreciated.
>
> Below is the error when I get the interface stats.
>
> vpp# show hardware-interfaces VirtualFuncEthernet0/6/0 detail
>               Name                Idx   Link  Hardware
> VirtualFuncEthernet0/6/0           3     up   VirtualFuncEthernet0/6/0
>   Link speed: 25 Gbps
>   RX Queues:
>     queue thread         mode
>     0     vpp_wk_0 (1)   polling
>   TX Queues:
>     TX Hash: [name: hash-eth-l34 priority: 50 description: Hash ethernet
> L34 headers]
>     queue shared thread(s)
>     0     no     0
>     1     no     1
>     2     no     2
>     3     no     3
>     4     no     4
>     5     no     5
>     6     no     6
>   Ethernet address fa:16:3e:f7:ea:8d
>   Intel iAVF
>     carrier up full duplex max-frame-size 1522
>     flags: admin-up subif tx-offload intel-phdr-cksum rx-ip4-cksum
> int-supported int-unmaskable
>     Devargs:
>     rx: queues 1 (max 256), desc 4096 (min 64 max 4096 align 32)
>     tx: queues 7 (max 256), desc 4096 (min 64 max 4096 align 32)
>     pci: device 8086:154c subsystem 1590:0000 address 0000:00:06.00 numa 0
>     module: unknown
>     max rx packet len: 9728
>     promiscuous: unicast off all-multicast on
>     vlan offload: strip off filter off qinq off
>     rx offload avail:  vlan-strip ipv4-cksum udp-cksum tcp-cksum qinq-strip
>                        outer-ipv4-cksum vlan-filter vlan-extend scatter
> rss-hash
>     rx offload active: ipv4-cksum
>     tx offload avail:  vlan-insert ipv4-cksum udp-cksum tcp-cksum
> sctp-cksum
>                        tcp-tso outer-ipv4-cksum qinq-insert vxlan-tnl-tso
>                        gre-tnl-tso ipip-tnl-tso geneve-tnl-tso multi-segs
>                        mbuf-fast-free outer-udp-cksum
>     tx offload active: ipv4-cksum udp-cksum tcp-cksum
>     rss avail:         ipv4-frag ipv4-tcp ipv4-udp ipv4-sctp ipv4-other
> ipv4
>                        ipv6-frag ipv6-tcp ipv6-udp ipv6-sctp ipv6-other
> ipv6
>     rss active:        none
>     tx burst function: (not available)
>     rx burst function: (not available)
>
>     tx frames ok                                          52
>     tx bytes ok                                         7414
>     tx errors                                              1
>     rx frames ok                                      175054
>     rx bytes ok                                     60125207
>     extended stats:
>       rx_good_packets                                 175054
>       tx_good_packets                                     52
>       rx_good_bytes                                 60125207
>       tx_good_bytes                                     7414
>       rx_missed_errors                                     0
>       rx_errors                                            0
>     *  tx_errors  *                                          1  ===> ESP
> Paket drop
>       rx_mbuf_allocation_errors                            0
>       rx_bytes                                      60825423
>       rx_unicast_packets                                  48
>       rx_multicast_packets                                 0
>       rx_broadcast_packets                            175006
>       rx_dropped_packets                                   0
>       rx_unknown_protocol_packets                          0
>       tx_bytes                                          7414
>       tx_unicast_packets                                  48
>       tx_multicast_packets                                 4
>       tx_broadcast_packets                                 0
>       tx_dropped_packets                                   0
>   *    tx_error_packets       *                              1  ===> ESP
> Paket drop
>       inline_ipsec_crypto_ipackets                         0
>       inline_ipsec_crypto_ibytes                           0
>       inline_ipsec_crypto_ierrors                          0
>       inline_ipsec_crypto_ierrors_sad_lookup               0
>       inline_ipsec_crypto_ierrors_not_proces               0
>       inline_ipsec_crypto_ierrors_icv_fail                 0
>       inline_ipsec_crypto_ierrors_length                   0
>       inline_ipsec_crypto_ierrors_misc                     0
> vpp#
>
>
>
>
> --
> Regards,
> sagar g
>


-- 
Regards,
sagar g

[-- Attachment #2: Type: text/html, Size: 14395 bytes --]

           reply	other threads:[~2024-02-29 18:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAOCi-21JP-dt6-8SfC_2UKM+jdGqv2N47JHu6grMN2GYSORieQ@mail.gmail.com>]

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=CAOCi-21qMaFa3KZ8mJCVYV4PZd6jZ-f9NyJ-tOE6qCUTorf-GA@mail.gmail.com \
    --to=sagargadher@gmail.com \
    --cc=dev@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).