From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Fwd: [Mcast-wifi] Issues with MLD and Android powersaving / sleep mode...
Date: Tue, 24 Mar 2020 22:01:49 +0100 [thread overview]
Message-ID: <20200324210149.GE2357@otheros> (raw)
And speaking of adoption and experiences, an annoying issue with
MLD+Android we came across lately.
In case someone would like to participate and help on this, too.
Implementing some workaround in the Linux bridge might be
something worth to consider, too.
----- Forwarded message from Linus Lüssing <linus.luessing@c0d3.blue> -----
Date: Tue, 24 Mar 2020 21:54:02 +0100
From: Linus Lüssing <linus.luessing@c0d3.blue>
To: mcast-wifi@ietf.org, pim@ietf.org
Subject: [Mcast-wifi] Issues with MLD and Android powersaving / sleep mode...
Hi,
With Freifunk [0] we lately came across an annoying issue with Android
devices... which I'm not really sure how to solve yet...
It seems that (some?) Android devices do not respond to MLD
queries when in sleep mode:
https://github.com/freifunk-gluon/gluon/issues/1832
https://issuetracker.google.com/issues/149630944
Which causes severe IPv6 connectivity/usability issues
when trying to use MLD snooping capabilities.
As soon as you turn on the screen of the Android device or
connect a charger MLD Reports arrive just fine. My test results
were, as noted in the Android ticket:
Results with phone on battery:
* 0/8 MLD Reports received
* 3/8 Neighbor Advertisements received
* 8/8 Echo Replies received
Results with phone on charger:
* 8/8 MLD Reports received
* 8/8 Neighbor Advertisements received
* 8/8 Echo Replies received
Fixing this on the Android devices would need several years to
propagate, as noted by an Android dev.
Has anyone on this list experienced similar issues, too? And is
there maybe even someone who came up with a workaround that they
implemented on the router/switch side?
If not and if we can't come up with a solution it looks pretty
gloomy for (non-flooding) multicast in wifi networks to me for
the next years...
Regards, Linus
[0]: https://freifunk.net/en/
_______________________________________________
Mcast-wifi mailing list
Mcast-wifi@ietf.org
https://www.ietf.org/mailman/listinfo/mcast-wifi
----- End forwarded message -----
reply other threads:[~2020-03-24 21:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200324210149.GE2357@otheros \
--to=linus.luessing@c0d3.blue \
--cc=bridge@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox