All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:41:39 -0700	[thread overview]
Message-ID: <0d76d387-ff27-eb8e-c37f-9a77f2b276b0@gmail.com> (raw)
In-Reply-To: <20180221192535.GA15987@splinter.mtl.com>

On 2/21/18 12:25 PM, Ido Schimmel wrote:
>>
>> and can talk to the hosts:
>> # ping6 ff02::2%br0
> 
> Can you try ff02::1 ?

same result.

> 
>> PING ff02::2%br0(ff02::2) 56 data bytes
>> 64 bytes from fe80::7efe:90ff:fee8:3a79: icmp_seq=1 ttl=64 time=0.073 ms
>> 64 bytes from fe80::202:ff:fe00:2: icmp_seq=1 ttl=64 time=0.661 ms (DUP!)
>> 64 bytes from fe80::202:ff:fe00:5: icmp_seq=1 ttl=64 time=0.705 ms (DUP!)
>> 64 bytes from fe80::202:ff:fe00:1: icmp_seq=1 ttl=64 time=0.720 ms (DUP!)
>> 64 bytes from fe80::202:ff:fe00:3: icmp_seq=1 ttl=64 time=0.729 ms (DUP!)
>> 64 bytes from fe80::202:ff:fe00:6: icmp_seq=1 ttl=64 time=0.739 ms (DUP!)
>> 64 bytes from fe80::202:ff:fe00:4: icmp_seq=1 ttl=64 time=0.748 ms (DUP!)
>> 64 bytes from fe80::202:ff:fe00:7: icmp_seq=1 ttl=64 time=0.757 ms (DUP!)
>> 64 bytes from fe80::202:ff:fe00:8: icmp_seq=1 ttl=64 time=0.766 ms (DUP!)
>>
>> but the hosts can not talk to each other:
>>
>> cumulus@host3:~$ net show lldp
>>
>> LocalPort  Speed  Mode          RemoteHost   RemotePort
>> ---------  -----  ------------  -----------  ----------
>> swp1       10G    Interface/L3  mlx-2700-05  swp1s2
>>
>> cumulus@host3:~$ ping6 3000:1000:1000:1000::2
>> PING 3000:1000:1000:1000::2(3000:1000:1000:1000::2) 56 data bytes
>> ^C
>> --- 3000:1000:1000:1000::2 ping statistics ---
>> 3 packets transmitted, 0 received, 100% packet loss, time 1999ms
> 
> Can you please try
> 
> # brctl showstp br0
> 
> To make sure STP state is set to forwarding?

it is.

> 
> 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.

  reply	other threads:[~2018-02-21 19:41 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 [this message]
2018-02-21 20:24       ` Ido Schimmel
2018-02-21 20:31         ` David Ahern
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=0d76d387-ff27-eb8e-c37f-9a77f2b276b0@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.