From: "Tj (Elloe Linux)" <ml.linux@elloe.vision>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vladimir Oltean <olteanv@gmail.com>,
netdev@vger.kernel.org, chris.packham@alliedtelesis.co.nz,
f.fainelli@gmail.com, marek.behun@nic.cz,
vivien.didelot@gmail.com, info <info@turris.cz>
Subject: Re: dsa: mv88e6xxx not receiving IPv6 multicast packets
Date: Mon, 16 Nov 2020 07:07:43 +0000 [thread overview]
Message-ID: <05b1c5de-3d1d-cc06-0e6a-e93e62c7a2c0@elloe.vision> (raw)
In-Reply-To: <20201115172705.GF1701029@lunn.ch>
On 15/11/2020 17:27, Andrew Lunn wrote:
> So check if you have an IGMP querier in the network. If not, try
> turning it on in the bridge,
>
> ip link set br0 type bridge mcast_querier 1
Thanks Andrew - that does indeed seem to have solved the issue.
I'm relieved this isn't a hardware or driver issue after all but annoyed
we didn't figure this out ourselves months ago!
Is there any other kernel 'nob' to alter this? I'm trying to understand
why we're seeing two different results with seemingly identical
kernel/OS versions and network configurations.
next prev parent reply other threads:[~2020-11-16 7:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 14:46 dsa: mv88e6xxx losing DHCPv6 solicit packets / IPv6 multicast packets? Marek Behún
2020-07-23 21:27 ` Chris Packham
2020-07-23 21:33 ` Florian Fainelli
2020-07-24 10:24 ` Tj (Elloe Linux)
2020-11-14 15:39 ` dsa: mv88e6xxx not receiving IPv6 multicast packets Tj (Elloe Linux)
2020-11-14 15:56 ` Andrew Lunn
2020-11-14 16:06 ` Tj (Elloe Linux)
2020-11-14 17:43 ` Marek Behun
2020-11-14 18:49 ` Vladimir Oltean
2020-11-15 10:53 ` Tj (Elloe Linux)
2020-11-15 16:02 ` Andrew Lunn
2020-11-15 17:19 ` Tj (Elloe Linux)
2020-11-15 17:27 ` Andrew Lunn
2020-11-16 7:07 ` Tj (Elloe Linux) [this message]
2020-11-16 10:45 ` Tj (Elloe Linux)
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=05b1c5de-3d1d-cc06-0e6a-e93e62c7a2c0@elloe.vision \
--to=ml.linux@elloe.vision \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=f.fainelli@gmail.com \
--cc=info@turris.cz \
--cc=marek.behun@nic.cz \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.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