From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>,
"Patrick Ruddy" <pruddy@vyatta.att-mail.com>
Cc: bridge@lists.linux-foundation.org,
Ido Schimmel <idosch@idosch.org>,
netdev@vger.kernel.org, roopa@cumulusnetworks.com
Subject: Re: [PATCH net-next] mcast: ensure L-L IPv6 packets are accepted by bridge
Date: Wed, 14 Aug 2019 23:34:47 +0300 [thread overview]
Message-ID: <d0be5038-e76f-d21b-a034-e450cbb3010e@cumulusnetworks.com> (raw)
In-Reply-To: <20190814201138.GE2431@otheros>
On 8/14/19 11:11 PM, Linus Lüssing wrote:
> On Wed, Aug 14, 2019 at 05:40:58PM +0100, Patrick Ruddy wrote:
>> The group is being joined by MLD at the L3 level but the packets are
>> not being passed up to the l3 interface becasue there is a MLD querier
>> on the network
>>
>> snippet from /proc/net/igmp6
>> ...
>> 40 sw1 ff0200000000000000000001ff008700 1 00000004 0
>> 40 sw1 ff020000000000000000000000000002 1 00000004 0
>> 40 sw1 ff020000000000000000000000000001 1 0000000C 0
>> 40 sw1 ff010000000000000000000000000001 1 00000008 0
>> 41 lo1 ff020000000000000000000000000001 1 0000000C 0
>> 41 lo1 ff010000000000000000000000000001 1 00000008 0
>> 42 sw1.1 ff020000000000000000000000000006 1 00000004 0
>> 42 sw1.1 ff020000000000000000000000000005 1 00000004 0
>> 42 sw1.1 ff0200000000000000000001ff000000 2 00000004 0
>> 42 sw1.1 ff0200000000000000000001ff008700 1 00000004 0
>> 42 sw1.1 ff0200000000000000000001ff000099 1 00000004 0
>> 42 sw1.1 ff020000000000000000000000000002 1 00000004 0
>> 42 sw1.1 ff020000000000000000000000000001 1 0000000C 0
>> 42 sw1.1 ff010000000000000000000000000001 1 00000008 0
>> ...
>>
>> the bridge is sw1 and the l3 intervace is sw1.1
>
> What kind of interface is sw1.1 exactly? Is it a VLAN or a VRF
> interface? Something else?
>
+1
> Could you also post the output of bridge mdb show?
>
> Regards, Linus
>
>
> PS: Also please include the bridge mailinglist in the future.
>
Note that if you'd like to debug a host joined group currently bridge mdb show
will not dump it and if the group is host-joined only it
can even be empty. You can use my latest set (not applied yet):
http://patchwork.ozlabs.org/project/netdev/list/?series=125169
Alternatively you could monitor the mdb events, it will show up there even
today without any changes (bridge monitor mdb) and you can check if it's
getting deleted.
Cheers,
Nik
next prev parent reply other threads:[~2019-08-14 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 14:18 [PATCH net-next] mcast: ensure L-L IPv6 packets are accepted by bridge Patrick Ruddy
2019-08-13 19:53 ` Ido Schimmel
2019-08-13 23:55 ` Nikolay Aleksandrov
2019-08-14 16:40 ` Patrick Ruddy
2019-08-14 16:58 ` Nikolay Aleksandrov
2019-08-14 20:11 ` Linus Lüssing
2019-08-14 20:34 ` Nikolay Aleksandrov [this message]
2019-08-15 13:36 ` Patrick Ruddy
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=d0be5038-e76f-d21b-a034-e450cbb3010e@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=idosch@idosch.org \
--cc=linus.luessing@c0d3.blue \
--cc=netdev@vger.kernel.org \
--cc=pruddy@vyatta.att-mail.com \
--cc=roopa@cumulusnetworks.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).