From: "Xing, Beilei" <beilei.xing@intel.com>
To: Alex Kiselev <kiselev99@gmail.com>,
"users@dpdk.org" <users@dpdk.org>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [dpdk-users] problem with an additional MAC address on i40e
Date: Thu, 24 May 2018 09:15:35 +0000 [thread overview]
Message-ID: <94479800C636CB44BD422CB454846E0132161CCA@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <351944790.20180522134228@gmail.com>
Hi Kiselev,
What's the firmware version you used? Did you try testpmd?
I tried testpmd with X710 on my side, the steps are:
testpmd> set fwd rxonly
testpmd> set verbose 1
testpmd> start
testpmd> mac_addr add 0 00:00:5E:00:01:0A
testpmd> stop
testpmd> start
After that, packets with destination 01:00:5E:00:00:12 still can be received.
Best Regards
Beilei Xing
> -----Original Message-----
> From: Alex Kiselev [mailto:kiselev99@gmail.com]
> Sent: Tuesday, May 22, 2018 6:42 PM
> To: users@dpdk.org; Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Subject: problem with an additional MAC address on i40e
>
> Hi.
>
> I am facing an issue trying to receive packets destined to the MAC address
> ipv4_mcast_12 01:00:5E:00:00:12.
>
> The problem is that once I add to a port additional MAC address
> 00:00:5E:00:01:0A using rte_eth_dev_mac_addr_add(), the port stop
> receiving packets destinated to the address 01:00:5E:00:00:12. When there
> is no additinal mac on a port everything is ok. Also, there is no such issue
> when I am using intel X520 nic (ixgbe), I am facing this behavior only with
> X710 (i40e) intel NIC.
>
> DPDK ver dpdk-stable-17.11.1
>
>
> --
> Alex Kiselev.
next prev parent reply other threads:[~2018-05-24 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 10:42 Alex Kiselev
2018-05-24 9:15 ` Xing, Beilei [this message]
2018-05-25 11:09 ` Alex Kiselev
2018-05-27 15:54 ` Alex Kiselev
2018-05-27 16:09 ` Alex Kiselev
2018-08-14 18:20 ` Ananda Sathyanarayana
2018-08-15 8:47 ` Alex Kiselev
2020-08-26 11:24 Mandeep Rohilla
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=94479800C636CB44BD422CB454846E0132161CCA@SHSMSX101.ccr.corp.intel.com \
--to=beilei.xing@intel.com \
--cc=kiselev99@gmail.com \
--cc=qi.z.zhang@intel.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).