>From my understanding the mac address assigned to the VF is used by the PF to >filter network traffic. This is intentional to isolate the VFs.
For this reason, your idea should not work. Todd Fujinaka Software Application Engineer Networking Division (ND) Intel Corporation todd.fujin...@intel.com (503) 712-4565 -----Original Message----- From: Roman Bogorodskiy [mailto:bogorods...@gmail.com] Sent: Wednesday, March 18, 2015 9:13 PM To: Fujinaka, Todd Cc: e1000-devel@lists.sourceforge.net Subject: Re: [E1000-devel] Controlling MAC address filtering on the host side Fujinaka, Todd wrote: > We don't allow more than one MAC address for a VF. Is that done intentionally or it's something that could be implemented in future? Also, is the way with macvlans I described in my original mail is legit at all? Thanks > -----Original Message----- > From: Roman Bogorodskiy [mailto:bogorods...@gmail.com] > Sent: Wednesday, March 18, 2015 6:11 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] Controlling MAC address filtering on the host > side > > Hi, > > I'm trying to find a way to assign more than one MAC address for a VF. > By assign I mean to allow a VM that's using this VF to be able to send > traffic with one of the specified MAC addresses and PF to route traffic for > the specific MAC address to a proper VF. > > I googled and found some email threads on the topic, but didn't find any > working solution for me. > > Currently, the only solution found looks this way: > > - before creating a VM, do not set a MAC address for VF that's going to > be attached to this VM (because the driver will set the 'pf_set_mac' > flag and will not allow further MAC-related changes [1]), i.e. don't > set it via 'ip link' or any other IFLA_VF_MAC based tools > - inside of this VM, new MAC address could be added by creating a > macvlan device, something like that: > > VM# ip link add link eth0 name mac0 type macvlan > VM# ip link set mac0 address aa:bb:cc:dd:ee:11 > > This solution does seem to work, however, it's pretty inconvenient for a > number of reasons. Probably the most important that if there's more than one > interface inside of a VM, there's no easy way to differentiate them without > proper MAC addresses assigned. > > I'm wondering if I'm missing something or it's indeed not possible to have a > scheme similar to described above, but from the host side? > > 1: > https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/int > el/ixgbe/ixgbe_sriov.c#L855 > > Thanks, > > Roman Bogorodskiy > > ---------------------------------------------------------------------- > -------- Dive into the World of Parallel Programming The Go Parallel > Website, sponsored by Intel and developed in partnership with Slashdot > Media, is your hub for all things parallel software development, from > weekly thought leadership blogs to news, videos, case studies, > tutorials and more. Take a look and join the conversation now. > http://goparallel.sourceforge.net/ > _______________________________________________ > E1000-devel mailing list > E1000-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired Roman Bogorodskiy ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
