netdev - Re: dsa/mv88e6xxx: leaking packets on MV88E6341 switch

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200930115705.GA12758@fido.de.innominate.com>
Date:   Wed, 30 Sep 2020 13:57:06 +0200
From:   Peter Vollmer <peter.vollmer@...il.com>
To:     Vladimir Oltean <olteanv@...il.com>
Cc:     Network Development <netdev@...r.kernel.org>
Subject: Re: dsa/mv88e6xxx: leaking packets on MV88E6341 switch

On Wed, Sep 30, 2020 at 01:28:35PM +0300, Vladimir Oltean wrote:
> On Wed, Sep 30, 2020 at 12:09:03PM +0200, Peter Vollmer wrote:
> > lan0..lan3 are members of the br0 bridge interface.
>
> and so is eth0, I assume?

No, eth0 is a dedicated interface with its own IP. We have routing between eth0 and br0.

root@...ard:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1024
    link/ether a8:74:1d:85:08:be brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1508 qdisc mq qlen 1024
    link/ether 00:a0:45:38:22:90 brd ff:ff:ff:ff:ff:ff
4: sit0@...E: <NOARP> mtu 1480 qdisc noop qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
5: lan0@...1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 qlen 1000
    link/ether a8:74:1d:85:08:bf brd ff:ff:ff:ff:ff:ff
6: lan1@...1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 qlen 1000
    link/ether a8:74:1d:85:08:c0 brd ff:ff:ff:ff:ff:ff
7: lan2@...1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 qlen 1000
    link/ether a8:74:1d:85:08:c1 brd ff:ff:ff:ff:ff:ff
8: lan3@...1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 qlen 1000
    link/ether a8:74:1d:85:08:c2 brd ff:ff:ff:ff:ff:ff
9: br0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
    link/ether a8:74:1d:85:08:bf brd ff:ff:ff:ff:ff:ff

root@...ard:~# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.a8741d8508bf       no              lan2
                                                        lan0
                                                        lan3
                                                        lan1


> > The problem is that for ICMP ping lan0-> eth0, ICMP ping request
> > packets are leaking (i.e. flooded)  to all other ports lan1..lan3,
> > while the ping reply eth0->lan0 arrives correctly at lan0 without any
> > leaked packets on lan1..lan3.
> 
> What are you pinging exactly, the IP of the eth0 interface, or a station
> connected to the eth0 which is part of the same bridge as the lan ports?
> 

I am pinging the address of a station connected to eth0 from a station
connected to switch port lan0.

Thanks,
Peter