DPDK patches and discussions
 help / color / mirror / Atom feed
From: Daeyoung Kim <kdy1029@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Receiving packets on only one port
Date: Fri, 26 Jun 2015 11:45:28 -0400	[thread overview]
Message-ID: <CAOFzDNxfQuOKk6y3MObdCAOOaW4fe_0B3pxUnvYCEYPqAZG+rg@mail.gmail.com> (raw)

Hello,

I'm writing a packet capture program from the l3fwd. When I send DNS
packets, the wireshark simultaneously gets all the packets on two ports.
However, using my program with promiscuous mode, one port receives all the
packets, but the other port gets nothing. Do you know why it happens? Could
it be network topology problem using DPDK, a DPDK design like forwarding
mechanism, or just my program bugs? Any comments would be appreciated.

Thanks,
Daeyoung

             reply	other threads:[~2015-06-26 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 15:45 Daeyoung Kim [this message]
2015-06-29  0:22 ` Keunhong Lee
2015-06-29 14:32   ` Daeyoung Kim
2015-06-29 15:28     ` Keunhong Lee
2015-06-29 15:39       ` Daeyoung Kim
2015-06-29 15:44         ` Keunhong Lee
2015-06-30 18:22           ` Daeyoung Kim

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=CAOFzDNxfQuOKk6y3MObdCAOOaW4fe_0B3pxUnvYCEYPqAZG+rg@mail.gmail.com \
    --to=kdy1029@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).