From: Dominic Chen <d.c.ddcc@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Same port receive/transmit loopback
Date: Mon, 20 Jan 2020 17:34:13 -0500 [thread overview]
Message-ID: <e4e89f7f-f75a-17b3-d197-221db5ebae33@gmail.com> (raw)
I've just started working with DPDK recently, and I'm a little confused
by the intended behavior when transmitting and receiving on the same port.
Currently, I haven't been able to receive the same packet that I
transmitted, regardless of the source/destination MACs on the Ethernet
packet (broadcast, self, etc), or whether the port is in promiscuous
mode. I've verified from other hosts on the network that my packets are
being sent, that I am able to receive packets (as long as I didn't send
them), and that I get the same behavior when using vfio-pci with both
e1000 and vmxnet3 (emulated in VMware).
Is there some built-in source MAC filtering that I'm missing? Or do I
have to enable loopback mode?
Thanks,
Dominic
next reply other threads:[~2020-01-20 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 22:34 Dominic Chen [this message]
2020-01-21 5:47 ` Muhammad Zain-ul-Abideen
2020-01-22 5:13 ` Dominic Chen
2020-01-23 18:25 ` Muhammad Zain-ul-Abideen
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=e4e89f7f-f75a-17b3-d197-221db5ebae33@gmail.com \
--to=d.c.ddcc@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).