DPDK patches and discussions
 help / color / mirror / Atom feed
From: Daeyoung Kim <kdy1029@gmail.com>
To: Keunhong Lee <dlrmsghd@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Receiving packets on only one port
Date: Mon, 29 Jun 2015 10:32:33 -0400	[thread overview]
Message-ID: <CAOFzDNyox33TTDzixHmnwpdiNUn9gxp47UbbX8jPuiAgqK_stQ@mail.gmail.com> (raw)
In-Reply-To: <CAKBXKmDoev0QV8noK=Rk8aSTsyLrBd1mUiiCwVoq-j01LiYL0A@mail.gmail.com>

Hi Keunhong,

Thank you for your help. Here is the network topology.

DNS Client - Switch 1 - Switch 2 - Switch 3 - DNS Server
                             |                                  |
                         port 0                          port 1

DPDK port 0 receives packets using from the Switch 1 port mirroring and
port 1 receives packets from the Switch 2 using port mirroring as well. As
I already said, when I send DNS packets, the wireshark simultaneously gets
all the packets on two ports. I'm sorry what I told you is incorrect. Using
my program with promiscuous mode, the port 0 receives only DNS queries from
the DNS client, but the port 1 receives only DNS replies from the DNS
server. I'd like to know why it happens.

Thank you very much!

Regards,
Daeyoung

2015-06-28 20:22 GMT-04:00 Keunhong Lee <dlrmsghd@gmail.com>:

> I don't know your situation exactly, but here are possible problems.
>
> 1. Your switch learned MAC addresses of two ports.
> 2. Your program bug.
> 3. l3fwd itself contains some bug.
> 4. You did not set all ports in promiscuous mode.
>
> You'd better try 'pktgen' application to test your environment.
>
> Keunhong.
>
>
>
> 2015-06-27 0:45 GMT+09:00 Daeyoung Kim <kdy1029@gmail.com>:
>
>> 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-29 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 15:45 Daeyoung Kim
2015-06-29  0:22 ` Keunhong Lee
2015-06-29 14:32   ` Daeyoung Kim [this message]
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=CAOFzDNyox33TTDzixHmnwpdiNUn9gxp47UbbX8jPuiAgqK_stQ@mail.gmail.com \
    --to=kdy1029@gmail.com \
    --cc=dev@dpdk.org \
    --cc=dlrmsghd@gmail.com \
    /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).