From: Stephen Hemminger <stephen@networkplumber.org>
To: Sagar Singha <singha.sagar09@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] After changing Destination MAC address in dpdk packet not reaching to destination
Date: Tue, 5 Sep 2017 09:23:33 -0700 [thread overview]
Message-ID: <20170905092333.67f9bb3b@xeon-e3> (raw)
In-Reply-To: <CAKXXrHcEV7c8pROuN8aRcKSLuV3omrZwiigHT=sNUDsZzKncAg@mail.gmail.com>
On Tue, 5 Sep 2017 11:56:36 +0530
Sagar Singha <singha.sagar09@gmail.com> wrote:
> Hi,
>
> I am using VMXNET3 type VM .OS distro=UBUNTU14.04.
> My VM is having 4 core CPU
> 4 GB RAM
>
> In l2fwd application in dpdk source code after receiving the packet I am
> changing the Destination MAC address.
>
> The below is my set UP:
>
> 1.Pinging from one VM having IP:10.0.102.72;MAC ADDR: 00:0c:29:f2:a7:7e
>
> 2.One VM from where I am running dpdk l2fwd application having three
> virtual interfaces: ens160(IP:10.0.102.166),
> ens192(IP:10.0.102.81),ens224(10.0.102.123)
> ens192 and ens224 I have binded with dpdk driver (igb_uio)
>
> 3.Another one VM to which I want send the packet by changing the MAC
> address in dpdk application having IP:10.0.102.106;MAC ADDR:
> 00:50:56:a8:6a:d4
>
> The packet I can see in the dpdk application as==
> source IP:10.0.102.72
> Dest IP:10.0.102.81
>
> Now before tx I am changing the dest mac addr for every packet with
> 00:50:56:a8:6a:d4.
> So Ideally It should reach to the dest.
>
> I am running tcpdump on the destination machine but there is no packet
> form 10.0.102.72
> from where I am pinging.
>
> The command I am running to run the app:
> ./build/app/l2fwd -c 3 -n 2 -- -p3 --no-mac-updating
>
>
> Please any clue!!!Thanks in advance!!
>
VMWare has host side MAC address filters which would block this by default.
There is some setting to allow guest to override MAC, but it has to be
configured on VSphere host side.
prev parent reply other threads:[~2017-09-05 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 6:26 Sagar Singha
2017-09-05 16:23 ` Stephen Hemminger [this message]
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=20170905092333.67f9bb3b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=singha.sagar09@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).