netdev - RE: ixgbe and mac-vlans problem

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-prev] [day] [month] [year] [list]

Message-ID: <EA929A9653AAE14F841771FB1DE5A1365FEA6DBA5F@rrsmsx501.amr.corp.intel.com>
Date:	Fri, 7 May 2010 11:40:29 -0600
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	Ben Greear <greearb@...delatech.com>
CC:	Arnd Bergmann <arnd@...db.de>, NetDev <netdev@...r.kernel.org>,
	Patrick McHardy <kaber@...sh.net>
Subject: RE: ixgbe and mac-vlans problem

Ben Greear wrote:
> On 05/06/2010 05:06 PM, Tantilov, Emil S wrote:
>> Ben Greear wrote:
>>> On 05/06/2010 10:51 AM, Tantilov, Emil S wrote:
>>> 
>>>> Hi Ben,
>>>> 
>>>> We do have a patch in testing (see attached). It may not apply
>>>> cleanly as it is on top of some other patches currently in
>>>> validation. Let me know if it works for you.
>>> 
>>> It wasn't difficult to backport this patch to 2.6.31.12....
>>> 
>>> I just tested this on an 85998 NIC and 50 MAC-VLANs worked fine.
>>> 
>>> The NIC doesn't show as PROMISC in any way I can detect, but I guess
>>> it must actually be in PROMISC mode:
>> 
>> Yes the interface is in promisc mode. The driver sets the FCTRL.UPE
>> bit (unicast promisc mode) when the number of allowed rar_entries is
>> exceeded. 
> 
> Is there any way to get this setting from ethtool or similar?  It
> would be nice to know the actual PROMISC state of the NIC regardless of
> what user-space has or has not configured.

ethtool -d eth11 | grep -i promisc 

Thanks,
Emil

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