[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2b53d14-7258-0137-79bc-b0a21ccc7b8f@gmail.com>
Date: Tue, 18 Feb 2020 16:00:08 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Russell King - ARM Linux admin <linux@...linux.org.uk>,
Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
Ido Schimmel <idosch@...sch.org>,
Vivien Didelot <vivien.didelot@...il.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Ivan Vecera <ivecera@...hat.com>,
Jakub Kicinski <kuba@...nel.org>,
Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/3] VLANs, DSA switches and multiple bridges
On 2/18/20 3:45 AM, Russell King - ARM Linux admin wrote:
> Hi,
>
> This is a repost of the previously posted RFC back in December, which
> did not get fully reviewed. I've dropped the RFC tag this time as no
> one really found anything too problematical in the RFC posting.
>
> I've been trying to configure DSA for VLANs and not having much success.
> The setup is quite simple:
>
> - The main network is untagged
> - The wifi network is a vlan tagged with id $VN running over the main
> network.
>
> I have an Armada 388 Clearfog with a PCIe wifi card which I'm trying to
> setup to provide wifi access to the vlan $VN network, while the switch
> is also part of the main network.
Why not just revert 2ea7a679ca2abd251c1ec03f20508619707e1749 ("net: dsa:
Don't add vlans when vlan filtering is disabled")? If a driver wants to
veto the programming of VLANs while it has ports enslaved to a bridge
that does not have VLAN filtering, it should have enough information to
not do that operation.
--
Florian
Powered by blists - more mailing lists