From: David Ahern <dsahern@gmail.com>
To: Ido Schimmel <idosch@idosch.org>
Cc: David Miller <davem@davemloft.net>,
jiri@resnulli.us, netdev@vger.kernel.org, idosch@mellanox.com,
mlxsw@mellanox.com
Subject: Re: [patch net-next] mlxsw: spectrum_switchdev: Allow port enslavement to a VLAN-unaware bridge
Date: Thu, 22 Feb 2018 14:48:08 -0700 [thread overview]
Message-ID: <fe47a943-1378-50c6-a980-1a96c053576e@gmail.com> (raw)
In-Reply-To: <20180222205543.GA21136@splinter>
On 2/22/18 1:55 PM, Ido Schimmel wrote:
> On Thu, Feb 22, 2018 at 12:27:35PM -0700, David Ahern wrote:
>> Ido:
>>
>> IPv4 works at boot; IPv6 requires the mcast snooping disable. For this
>> vlan-unaware bridges can that be set automatically?
>
> Can you please try the following patch?
>
...
>
> It should fix your problem.
it does.
>
> The real problem that I can then address in net-next is the fact that
> the Linux bridge tries to be smart and only resorts to flooding
> unregistered multicast packets in case its querier is disabled and in
> case it didn't detect any other querier in the network. This isn't
> currently reflected to underlying drivers. Only mcast snooping on/off.
>
> Anyway, it's not related to the patch in question. You'd get the same
> behavior with VLAN-aware bridges.
>
>> And then, what are the options for lldp?
>
> Didn't understand the question. Can you clarify?
>
nm. mental lapse.
next prev parent reply other threads:[~2018-02-22 21:48 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
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 [this message]
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=fe47a943-1378-50c6-a980-1a96c053576e@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.