netdev - Re: mv88e6321, dual cpu port

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: <9f12a869-04b0-60a3-c773-082b80d5df35@kernel-space.org>
Date:   Thu, 16 Feb 2023 15:24:23 +0100
From:   Angelo Dureghello <angelo@...nel-space.org>
To:     Vladimir Oltean <olteanv@...il.com>
Cc:     Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org
Subject: Re: mv88e6321, dual cpu port

Hi Andrew and Vladimir,

thanks, it works.

Attaching the final script (dts as avobe) if you want to
double check, and in case of any interest.

On 16/02/23 1:50 PM, Vladimir Oltean wrote:
 > On Thu, Feb 16, 2023 at 12:20:24PM +0100, Angelo Dureghello wrote:
 >> Still data passes all trough port6, even when i ping from
 >> host PC to port4. I was expecting instead to see port5
 >> statistics increasing.
 >
 >> # configure the bridge
 >> ip addr add 192.0.2.1/25 dev br0
 >> ip addr add 192.0.2.129/25 dev br1
 >
 > In this configuration you're supposed to put an IP address on the fec2
 > interface (eth1), not on br1.
 >
 > br1 will handle offloaded forwarding between port5 and the external
 > ports (port3, port4). It doesn't need an IP address. In fact, if you
 > give it an IP address, you will make the sent packets go through the br1
 > interface, which does dev_queue_xmit() to the bridge ports (port3, port4,
 > port5), ports which are DSA, so they do dev_queue_xmit() through their
 > DSA master - eth0. So the system behaves as instructed.
#!/bin/sh
#
# Configuration:
#                                       +---- port0
#              br0 eth0  <->   port 6  -+---- port1
#                                       +---- port2
#
#                                       +---- port3
#              br1 eth1  <-> --------- -+-----port4
#                                       +---- port5
#
# tested, port4 ping, data passes always from port 6
#

ip link set eth0 up
ip link set eth1 up

# bring up the slave interfaces
ip link set port0 up
ip link set port1 up
ip link set port2 up
ip link set port3 up
ip link set port4 up
ip link set port5 up

# create bridge
ip link add name br0 type bridge
ip link add name br1 type bridge

# add ports to bridge
ip link set dev port0 master br0
ip link set dev port1 master br0
ip link set dev port2 master br0

ip link set dev port3 master br1
ip link set dev port4 master br1
ip link set dev port5 master br1

# configure the bridge
ip addr add 192.0.2.1/25 dev br0
ip addr add 192.0.2.129/25 dev eth1

# bring up the bridge
ip link set dev br0 up
ip link set dev br1 up

Many thanks !
-- 
Angelo Dureghello