From: "Wiles, Keith" <keith.wiles@intel.com>
To: Padam Jeet Singh <padam.singh@inventum.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Unable to change source MAC address of packet
Date: Thu, 27 Oct 2016 14:07:58 +0000 [thread overview]
Message-ID: <DCD7B69C-9945-4C4B-AAA3-119F4F88D2CE@intel.com> (raw)
In-Reply-To: <73B7F896-A39A-4805-915B-6B7E80994681@inventum.net>
> On Oct 27, 2016, at 6:33 AM, Padam Jeet Singh <padam.singh@inventum.net> wrote:
>
> Hi,
>
> I am crafting a packet in which the source MAC address as set in the Ethernet header is different than the transmit port’s default MAC address. A packet capture of the packets coming out of this port however comes with source MAC address of the port’s default MAC address.
>
> Altering the destination MAC address works fine and shows up correctly in packet capture.
>
> The underlying network interface is an i210 and some logs added to the eth_igb_xmit_pkts function show that the packets I have crafted indeed are reaching the driver with the source MAC address set in the packet code of the application.
>
> How can I disable this automatic source MAC address setting?
The packets sent with rte_eth_tx_burst() are not forced to a give MAC address. If you are using something on top of DPDK like Pktgen or OVS or something, then it may try to force a source MAC address. Maybe the hardware does it, but we need to know the NIC being used and then someone maybe able to answer. I do not know of any Intel NICs do that.
Is this what you are doing.
>
> Thanks,
> Padam
Regards,
Keith
next prev parent reply other threads:[~2016-10-27 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 13:33 Padam Jeet Singh
2016-10-27 14:07 ` Wiles, Keith [this message]
2016-10-27 14:45 ` Padam Jeet Singh
2016-10-28 5:57 ` Lu, Wenzhuo
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=DCD7B69C-9945-4C4B-AAA3-119F4F88D2CE@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=padam.singh@inventum.net \
/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).