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]

Date:   Tue, 22 May 2018 12:15:31 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Gerhard Wiesinger <lists@...singer.com>,
        Andrew Lunn <andrew@...n.ch>, linux-kernel@...r.kernel.org
Subject: Re: B53 DSA switch problem on Banana Pi-R1 on Fedora 26

Hi,

On 05/22/2018 12:11 PM, Gerhard Wiesinger wrote:
> Hello,
> 
> I'm trying to get B53 DSA switch working on the Banana Pi-R1 on Fedora
> 26 to run (I will upgrade to Fedora 27 and Fedora 28 when networking
> works again). Previously the switch was configured with swconfig without
> any problems.
> 
> Kernel: 4.16.7-100.fc26.armv7hl
> 
> b53_common: found switch: BCM53125, rev 4
> 
> I see all interfaces: lan1 to lan4 and wan.
> 
> i get the following error messages:
> 
> # master and self, same results
> 
> bridge vlan add dev lan1 vid 101 pvid untagged self
> RTNETLINK answers: Operation not supported
> bridge vlan add dev lan2 vid 101 pvid untagged self
> RTNETLINK answers: Operation not supported
> bridge vlan add dev lan3 vid 101 pvid untagged self
> RTNETLINK answers: Operation not supported
> bridge vlan add dev lan4 vid 101 pvid untagged self
> RTNETLINK answers: Operation not supported
> 
> # No quite sure here regarding CPU interface and VLAN, because this
> changed with some patches, also from dsa.txt
> 
> bridge vlan add dev eth0 vid 101 self
> RTNETLINK answers: Operation not supported

That won't work, eth0 is the master DSA device, if you need to create a
VLAN on top it would be with vconfig and/or ip link

> 
> 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)
> 
> I think the rest of the config is clear after some research now, but I
> provide details if that one worked well.
> 
> If necessary I can provide full commands & logs and further details.
> 
> Thank you.
> 
> Any ideas?

Do you have CONFIG_BRIDGE_VLAN_FILTERING=y enabled in your kernel?

> 
> Ciao,
> 
> Gerhard
> 
> 


-- 
Florian