From: Andrew Lunn <andrew@lunn.ch>
To: "Tj (Elloe Linux)" <ml.linux@elloe.vision>
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: Sun, 15 Nov 2020 18:27:05 +0100 [thread overview]
Message-ID: <20201115172705.GF1701029@lunn.ch> (raw)
In-Reply-To: <79ad87d1-15e0-7ccc-e1ad-4aab3fdf0d20@elloe.vision>
> Using tcpdump I *think* enp2s0 (wired link direct into lan1 on 'good')
> always showed the laptop sending multicast listener report v2 packets on
> a regular cadence of about 60-100 seconds as well as the DHCPv6
> solicit/renews and that cadence matched when the timers on the output of
> "bridge -d -s mdb show" reset to approximately 258.
>
> But for wlp4s0 (wifi to 'bad') the DHCPv6 solicit/renew didn't seem to
> be accompanied by multicast listener reports and the mdb timers expired.
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
Andrew
next prev parent reply other threads:[~2020-11-15 17:32 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 [this message]
2020-11-16 7:07 ` Tj (Elloe Linux)
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=20201115172705.GF1701029@lunn.ch \
--to=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=f.fainelli@gmail.com \
--cc=info@turris.cz \
--cc=marek.behun@nic.cz \
--cc=ml.linux@elloe.vision \
--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;
as well as URLs for NNTP newsgroup(s).