linux-kernel - Re: B53 DSA switch problem on Banana Pi-R1 on Fedora 26

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]

Message-ID: <59d6b55f-d50a-063c-90a9-31a758e01383@gmail.com>
Date:   Tue, 22 May 2018 13:42:40 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Andrew Lunn <andrew@...n.ch>,
        Gerhard Wiesinger <lists@...singer.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: B53 DSA switch problem on Banana Pi-R1 on Fedora 26

On 05/22/2018 01:16 PM, Andrew Lunn wrote:
>> Planned network structure will be as with 4.7.x kernels:
>>
>> br0 <=> eth0.101 <=> eth0 (vlan 101 tagged) <=> lan 1-lan4 (vlan 101
>> untagged pvid)
>>
>> br1 <=> eth0.102 <=> eth0 (vlan 102 tagged) <=> wan (vlan 102 untagged pvid)
> 
> Do you even need these vlans?

Yes, remember, b53 does not currently turn on Broadcom tags, so the only
way to segregate traffic is to have VLANs for that.

> 
> Are you doing this for port separation? To keep lan1-4 traffic
> separate from wan? DSA does that by default, no vlan needed.
> 
> So you can just do
> 
> ip link add name br0 type bridge
> ip link set dev br0 up
> ip link set dev lan1 master br0
> ip link set dev lan2 master br0
> ip link set dev lan3 master br0
> ip link set dev lan4 master br0
> 
> and use interface wan directly, no bridge needed.

That would work once Broadcom tags are turned on which requires turning
on managed mode, which requires work that I have not been able to get
done :)
-- 
Florian