netdev - Re: [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support

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: <20090807143652.1659ac57@nehalam>
Date:	Fri, 7 Aug 2009 14:36:52 -0700
From:	Stephen Hemminger <shemminger@...ux-foundation.org>
To:	"Paul Congdon \(UC Davis\)" <ptcongdon@...avis.edu>
Cc:	<anna.fischer@...com>, <bridge@...ts.linux-foundation.org>,
	<netdev@...r.kernel.org>,
	<virtualization@...ts.linux-foundation.org>, <davem@...emloft.net>,
	<kaber@...sh.net>, <adobriyan@...il.com>, <arnd@...db.de>
Subject: Re: [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support

On Fri, 7 Aug 2009 14:06:58 -0700
"Paul Congdon \(UC Davis\)" <ptcongdon@...avis.edu> wrote:

> Yaron,
> 
> 
> The interface multiplexing can be achieved using macvlan driver or using an SR-IOV capable NIC (the preferred option), macvlan may need to be extended to support VEPA multicast handling, this looks like a rather simple task 
> 
> Agreed that the hardware solution is preferred so the macvlan implementation doesn’t really matter.  If we are talking SR-IOV, then it is direct mapped, regardless of whether there is a VEB or VEPA in the hardware below, so you are bypassing the bridge software code also.  
> 
> I disagree that adding the multicast handling is simple – while not conceptually hard, it will basically require you to put an address table into the macvlan implementation – if you have that, then why not have just used the one already in the bridge code.  If you hook a VEPA up to a non-hairpin mode external bridge, you get the macvlan capability as well.

I have a patch that forwards all multicast packets, and another that does
proper forwarding. It should have worked that way in original macvlan, the
current behavior is really a bug.


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