From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Patrick Ruddy <pruddy@vyatta.att-mail.com>
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
Ido Schimmel <idosch@idosch.org>,
roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [Bridge] [PATCH net-next] mcast: ensure L-L IPv6 packets are accepted by bridge
Date: Wed, 14 Aug 2019 22:11:38 +0200 [thread overview]
Message-ID: <20190814201138.GE2431@otheros> (raw)
In-Reply-To: <620d3cfbe58e3ae87ef1d5e7f2aa1588cac3e64a.camel@vyatta.att-mail.com>
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?
Could you also post the output of bridge mdb show?
Regards, Linus
PS: Also please include the bridge mailinglist in the future.
next parent reply other threads:[~2019-08-14 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190813141804.20515-1-pruddy@vyatta.att-mail.com>
[not found] ` <20190813195341.GA27005@splinter>
[not found] ` <43ed59db-9228-9132-b9a5-31c8d1e8e9e9@cumulusnetworks.com>
[not found] ` <620d3cfbe58e3ae87ef1d5e7f2aa1588cac3e64a.camel@vyatta.att-mail.com>
2019-08-14 20:11 ` Linus Lüssing [this message]
2019-08-14 20:34 ` [Bridge] [PATCH net-next] mcast: ensure L-L IPv6 packets are accepted by bridge Nikolay Aleksandrov
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=20190814201138.GE2431@otheros \
--to=linus.luessing@c0d3.blue \
--cc=bridge@lists.linux-foundation.org \
--cc=idosch@idosch.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--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