netdev - ixgbe: SR-IOV, macvlan filter on VFs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <53ECA5C9.2020904@univ-nantes.fr>
Date:	Thu, 14 Aug 2014 14:04:25 +0200
From:	Yoann Juet <veilletechno-irts@...v-nantes.fr>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	Yoann Juet <yoann.juet@...v-nantes.fr>
Subject: ixgbe: SR-IOV, macvlan filter on VFs

Hi all,

We are trying to make VRRP with VMAC address work on VMs using SR-IOV. 
The well known Keepalived VRRP framework implements such a feature with 
a macvlan device per physical interface. In our setup, this means we get 
a new macvlan device per VF. To make it partially work, we first have to 
disable the ixgbe anti-spoofing feature on the PFs that are involved:

ip link set dev <ethX> vf <x> spoofchk off

Now, VIPs' Virtual Mac Address are known from clients (arp answers are 
transmitted). But this is not enough ; VIPs are still not reachable from 
clients as they are attached to a macvlan device. Each time a VMAC is 
set on a macvlan device, we get the following messages:

[674943.437989] ixgbe 0000:04:00.0 eth2: VF 0 requested MACVLAN filter 
but is administratively denied
[674943.458875] ixgbe 0000:04:00.0 eth2: VF 1 requested MACVLAN filter 
but is administratively denied

Looks like macvlan on VF only works for outbound traffic from VMs. 
Inbound traffic is filtered. Is there a solution to disable macvlan 
filtering on a VF basis ?

Thanks,
Best Regards,

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html