From: David Ahern <dsahern@gmail.com>
To: Ido Schimmel <idosch@idosch.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, davem@davemloft.net, idosch@mellanox.com,
mlxsw@mellanox.com
Subject: Re: [patch net-next] mlxsw: spectrum_switchdev: Allow port enslavement to a VLAN-unaware bridge
Date: Wed, 21 Feb 2018 13:31:40 -0700 [thread overview]
Message-ID: <c8873f57-349b-57e2-5ebb-c912c5d26cf1@gmail.com> (raw)
In-Reply-To: <20180221202432.GA18451@splinter.mtl.com>
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.
next prev parent reply other threads:[~2018-02-21 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 7:45 [patch net-next] mlxsw: spectrum_switchdev: Allow port enslavement to a VLAN-unaware bridge Jiri Pirko
2018-02-21 18:16 ` David Ahern
2018-02-21 19:25 ` Ido Schimmel
2018-02-21 19:41 ` David Ahern
2018-02-21 20:24 ` Ido Schimmel
2018-02-21 20:31 ` David Ahern [this message]
2018-02-22 18:58 ` David Miller
2018-02-22 19:27 ` David Ahern
2018-02-22 20:55 ` Ido Schimmel
2018-02-22 21:48 ` David Ahern
2018-02-26 6:54 ` Ido Schimmel
2018-02-26 16:12 ` David Miller
2018-02-26 16:08 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c8873f57-349b-57e2-5ebb-c912c5d26cf1@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.