netdev - RE: Which tool to use?

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

Date:	Thu, 28 Jan 2010 09:59:59 -0800
From:	"Rose, Gregory V" <gregory.v.rose@...el.com>
To:	"Williams, Mitch A" <mitch.a.williams@...el.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"davem@...emloft.net" <davem@...emloft.net>,
	Stephen Hemminger <shemminger@...tta.com>
Subject: RE: Which tool to use?

>-----Original Message-----
>From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
>On Behalf Of Williams, Mitch A
>Sent: Wednesday, January 27, 2010 10:10 PM
>To: netdev@...r.kernel.org; davem@...emloft.net; Stephen Hemminger
>Subject: Which tool to use?
>
>Which tool to use?
>
>Just looking for a bit of direction before I go off and start coding...
>
>Our SR-IOV capable parts (like everybody else's) include simple built-in
>Layer 2 switch, to allow packets to be switched between the various VF
>devices.
>
>We need the capability of configuring this switch from userspace. There
>are a few features we'd like to control, like anti-spoofing, and
>storm control, as well as being able to completely disable the internal
>switch for external loopback.  Mostly, however, we want to be able to
>add
>new MAC address filters to the switch.
>
>This is actually a pressing need, for SR-IOV to be really usable in
>a virtualized environment. In most use cases, along with VMs that are
>assigned VF devices, there will be a bunch of VMs talking through the PF
>device via a bridge.  We need to add the MAC addresses of these VMs to
>the on-board switch, or other VMs using the VF devices won't be able to
>talk to them - the packets will go out on the wire instead.
>
>So, which tool do I modify to make this happen? Ethtool, or ip?  I can
>think of convincing arguments for either, so I want to double-check with
>the maintainers before I dive in.
>
>Thanks,
>Mitch
>

The folks working on the Open vSwitch project are addressing some of these issues also.  You might want to check them out at openvswitch.org, although I have no idea what sort of view the Linux networking community has towards their work.

- Greg


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