DPDK usage discussions
 help / color / mirror / Atom feed
From: Haider Ali <haider@dreambigsemi.com>
To: users <users@dpdk.org>
Subject: link up / down not working with Mellanox
Date: Tue, 17 May 2022 06:46:43 +0000	[thread overview]
Message-ID: <MW5PR22MB339501DA92FB35A6801CD601A7CE9@MW5PR22MB3395.namprd22.prod.outlook.com> (raw)

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

Hi,

I am trying to test the link-up and link-down features of Mellanox using this link https://dpdk-test-plans.readthedocs.io/en/latest/shutdown_api_test_plan.html. But found that even after setting the link-down, NIC is forwarding the traffic. Please check my test setup:

Server 1:
$ sudo ./build/app/dpdk-testpmd -l 0,2 -n 4 --file-prefix=ha -a 0000:04:00.1 -- -i --rxq=1 --txq=1
testpmd> set fwd mac
testpmd> start
testpmd> set link-down port 0
Port 0: link state change event

Server 2:
>>> sendp(Ether()/IP()/TCP()/Raw('x'*300),iface='enp4s0f1')
$ sudo tcpdump -i enp4s0f1 -vve

22:59:52.469337 00:00:00:00:00:00 (oui Ethernet) > Broadcast, ethertype IPv4 (0x0800), length 354: (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto TCP (6), length 340)
    localhost.ftp-data > localhost.http: Flags [S], cksum 0xf9b9 (correct), seq 0:300, win 8192, length 300: HTTP

22:59:52.469379 b8:ce:f6:ed:9f:af (oui Unknown) > 02:00:00:00:00:00 (oui Unknown), ethertype IPv4 (0x0800), length 354: (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto TCP (6), length 340)
    localhost.ftp-data > localhost.http: Flags [S], cksum 0xf9b9 (correct), seq 0:300, win 8192, length 300: HTTP


Please correct me if I am doing anything wrong.

Regards,
Haider

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

             reply	other threads:[~2022-05-19 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17  6:46 Haider Ali [this message]
2022-06-06 10:24 ` Haider Ali

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=MW5PR22MB339501DA92FB35A6801CD601A7CE9@MW5PR22MB3395.namprd22.prod.outlook.com \
    --to=haider@dreambigsemi.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).