[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56D0CDCD.2040806@elecsyscorp.com>
Date: Fri, 26 Feb 2016 22:12:28 +0000
From: Kevin Smith <kevin.smith@...csyscorp.com>
To: Vivien Didelot <vivien.didelot@...oirfairelinux.com>,
Andrew Lunn <andrew@...n.ch>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kernel@...oirfairelinux.com" <kernel@...oirfairelinux.com>,
"David S. Miller" <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>,
Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
Guenter Roeck <linux@...ck-us.net>,
Neil Armstrong <narmstrong@...libre.com>,
Sascha Hauer <s.hauer@...gutronix.de>,
Russell King <rmk+kernel@....linux.org.uk>
Subject: Re: [PATCH net-next 7/9] net: dsa: mv88e6xxx: restore VLANTable map
control
Hi Vivien, Andrew,
On 02/26/2016 03:37 PM, Vivien Didelot wrote:
> Here, 5 is the CPU port and 6 is a DSA port.
>
> After joining ports 0, 1, 2 in the same bridge, we end up with:
>
> Port 0 1 2 3 4 5 6
> 0 - * * - - * *
> 1 * - * - - * *
> 2 * * - - - * *
> 3 - - - - - * *
> 4 - - - - - * *
> 5 * * * * * - *
> 6 * * * * * * -
The case I am concerned about is if the switch connected over DSA in
this example has a WAN port on it, which can legitimately route to the
CPU on port 5 but should not route to the LAN ports 0, 1, and 2. Does
this VLAN allow direct communication between the WAN and LAN? Or is
this prevented by DSA or some other mechanism?
Thanks,
Kevin
Powered by blists - more mailing lists