DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] After changing Destination MAC address in dpdk packet not reaching to destination
@ 2017-09-05  6:26 Sagar Singha
  2017-09-05 16:23 ` Stephen Hemminger
  0 siblings, 1 reply; 2+ messages in thread
From: Sagar Singha @ 2017-09-05  6:26 UTC (permalink / raw)
  To: users

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!!

-- 
Thanks & Regards,
Sagar Singha
Contact:7416733224
             9475209510

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-users] After changing Destination MAC address in dpdk packet not reaching to destination
  2017-09-05  6:26 [dpdk-users] After changing Destination MAC address in dpdk packet not reaching to destination Sagar Singha
@ 2017-09-05 16:23 ` Stephen Hemminger
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2017-09-05 16:23 UTC (permalink / raw)
  To: Sagar Singha; +Cc: users

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-09-05 16:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-09-05  6:26 [dpdk-users] After changing Destination MAC address in dpdk packet not reaching to destination Sagar Singha
2017-09-05 16:23 ` Stephen Hemminger

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).