From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f41.google.com ([209.85.160.41]:46487 "EHLO mail-pl0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750738AbeBUUbL (ORCPT ); Wed, 21 Feb 2018 15:31:11 -0500 Received: by mail-pl0-f41.google.com with SMTP id x19so1563446plr.13 for ; Wed, 21 Feb 2018 12:31:11 -0800 (PST) Subject: Re: [patch net-next] mlxsw: spectrum_switchdev: Allow port enslavement to a VLAN-unaware bridge To: Ido Schimmel Cc: Jiri Pirko , netdev@vger.kernel.org, davem@davemloft.net, idosch@mellanox.com, mlxsw@mellanox.com References: <20180220074512.4307-1-jiri@resnulli.us> <20180221192535.GA15987@splinter.mtl.com> <0d76d387-ff27-eb8e-c37f-9a77f2b276b0@gmail.com> <20180221202432.GA18451@splinter.mtl.com> From: David Ahern Message-ID: Date: Wed, 21 Feb 2018 13:31:40 -0700 MIME-Version: 1.0 In-Reply-To: <20180221202432.GA18451@splinter.mtl.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: On 2/21/18 1:24 PM, Ido Schimmel wrote: >>> Does it matter if you try IPv4 ping or if vlan_filtering is set 1? >>> Unfortunately, I can't reproduce on my switch. >> >> Bring up the hosts and then reboot the switch. At that point I get no >> host to host communication. As soon as I flap the port on host1 host3 to >> host1 starts working. >> >> So it seems to be something about the initial boot state. > > You didn't have IPv6 *and* IPv4 ping? I'm asking because it's possible > host1 sent an MLD join to the Solicited-node multicast address before > the bridge started listening, which means it didn't have a corresponding > MDB entry. The sim only configures IPv6, but it is not acting as an mcast router. It's really a dummy setup -- bridge on the switch, ports connected to hosts. > > Assuming your hosts aren't functioning as multicast routers and sending > MLD queries and that you didn't configure them as mrouter ports on the > switch, then when host3 sent a neighbour solicitation message to host1's > Solicited-node multicast address it wasn't flooded to host3 which > prevented ping from passing. > > This also explains why it started working when you flapped the port on > host1, as Linux generates MLD joins in these cases. > > You can try to disable snooping: > > # ip link set dev br0 type bridge mcast_snooping 0 > > Just a guess, but worth a try. good guess. That change gets it working.