netdev - mv88e6xxx: 88ae6321 not learning bridge mac address

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-next>] [day] [month] [year] [list]

Date:   Tue, 21 Sep 2021 11:02:43 +0200
From:   Bas Vermeulen <bvermeul@...ckstar.nl>
To:     netdev@...r.kernel.org
Cc:     andrew@...n.ch, vivien.didelot@...il.com
Subject: mv88e6xxx: 88ae6321 not learning bridge mac address

Hi,

I am working on a custom i.MX8 board using a Marvell 88ae6321 switch. 
We're not using the latest kernel unfortunately, but 5.4.70 with patches 
from NXP and ourselves.

The switch is connected as follows:

CPU - fec ethernet -> 88ae6321 on port 5, with external PHYs on port 1, 
2 and 6, and using the internal PHY on port 3 and 4.

We set up a bridge with swp1, swp2, swp3, swp4, and swp6. Traffic from 
the various ports all learn correctly, with the exception of the bridge 
itself (and probably the CPU port?).

If I ping the bridge address from one of the clients, the switch floods 
the ping request to all ports.
If I ping a client from the bridge address, the ping request goes to 
that client, the reply goes to all connected ports. This also happens if 
I use iperf3 to test the bandwidth, and will limit the bandwidth 
available when sending from the client to the lowest link on the switch.

Anyone have an idea how to fix this? It's possible I've misconfigured 
something, but I'm not sure what it could be. If there is a way to teach 
the 88ae6321 that a mac address is available on the CPU port, that would 
fix it, for instance. I tried adding the switch mac address with bridge 
fdb add, but that didn't work.

Regards,

Bas Vermeulen