test suite reviews and discussions
 help / color / mirror / Atom feed
From: David Liu <dliu@iol.unh.edu>
To: dev@dpdk.org, dts@dpdk.org
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
	David Liu <dliu@iol.unh.edu>,
	 David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	 Ferruh Yigit <ferruh.yigit@intel.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	 Ori Kam <orika@mellanox.com>,
	Ciara Power <ciara.power@intel.com>,
	 Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	 Stephen Hemminger <stephen@networkplumber.org>,
	Raslan Darawsheh <rasland@mellanox.com>
Subject: [dts] Promiscuous Mode Feature
Date: Wed, 24 Jun 2020 12:18:45 -0400	[thread overview]
Message-ID: <CAAuqQpQptwHz=QNiFV1MOdt4EiHJq91yNM0F6nDjADi-ox5BmQ@mail.gmail.com> (raw)

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

Hi all,

From my understanding, the promiscuous mode feature will verify the
functionality of promiscuous mode when it is on or off. The plan for
testing this feature is as follows:

Sending over a packet to verify the ports are working properly before any
testing. First to verify the promiscuous mode is enabled. With the
promiscuous being enabled, send over a packet and check if the packet will
be received when sending it to a different destination mac address than the
host/card. Then disable the promiscuous mode. The packet will only be
received if the mac address is the destination mac address. Otherwise, the
test case will be considered a failure.

Please let me know if there is anything I need to add on or if there are
certain cases I need to be aware of.

Thanks,
David Liu
UNH Interoperability Lab

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

                 reply	other threads:[~2020-06-24 16:19 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='CAAuqQpQptwHz=QNiFV1MOdt4EiHJq91yNM0F6nDjADi-ox5BmQ@mail.gmail.com' \
    --to=dliu@iol.unh.edu \
    --cc=arybchenko@solarflare.com \
    --cc=ciara.power@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=ivan.ilchenko@oktetlabs.ru \
    --cc=lylavoie@iol.unh.edu \
    --cc=orika@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).