Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753216AbbFDSW4 (ORCPT ); Thu, 4 Jun 2015 14:22:56 -0400 Received: from mail-qk0-f175.google.com ([209.85.220.175]:35964 "EHLO mail-qk0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752609AbbFDSWy (ORCPT ); Thu, 4 Jun 2015 14:22:54 -0400 Message-ID: <55709779.4040101@cumulusnetworks.com> Date: Thu, 04 Jun 2015 11:22:49 -0700 From: nolan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Scott Feldman CC: Guenter Roeck , Vivien Didelot , Netdev , "David S. Miller" , Florian Fainelli , Andrew Lunn , Jiri Pirko , Jerome Oufella , "linux-kernel@vger.kernel.org" , kernel , Chris Healy , Wilson Kok Subject: Re: [RFC 3/9] net: dsa: mv88e6xxx: add support for VTU ops References: <1433208470-25338-1-git-send-email-vivien.didelot@savoirfairelinux.com> <1433208470-25338-4-git-send-email-vivien.didelot@savoirfairelinux.com> <556D522E.90607@roeck-us.net> <556E2EC2.3020104@cumulusnetworks.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1411 Lines: 35 On 06/02/2015 11:53 PM, Scott Feldman wrote: > I'm talking about bridging tagged traffic. E.g.: > > ip link add name br0 type bridge > ip link add name br1 type bridge > > ip link set dev sw1p1 master br0 > ip link set dev sw1p2 master br0 > ip link set dev sw1p3 master br1 > ip link set dev sw1p4 master br1 > > bridge vlan add vid 100 dev sw1p1 > bridge vlan add vid 100 dev sw1p2 > bridge vlan add vid 100 dev sw1p3 > bridge vlan add vid 100 dev sw1p4 > > Now the ports are trunking vlan 100 and the bridge/device see tagged > traffic. If the device used floods vlan 100 pkt to all ports in vlan > 100, it'll flood to a port outside the bridge. Oops! For the device > I'm using (rocker w/ OF-DPA) the bridging table matches on vlan ID and > mac_dst. There is no prevision to isolate vlans per bridge. > > How do you solve the above case with your hardware? Ah, understood, thanks for clarifying. Right now, we only support this case with vconfig-style vlans. I don't see any conceptual reason it couldn't be supported in the vlan-aware bridge model as well. The HW configuration would be essentially identical to the equivalent vconfig-style config. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/