Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: netdev@vger.kernel.org,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
bridge@lists.linux-foundation.org, gluon@luebeck.freifunk.net,
openwrt-devel@lists.openwrt.org,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH net-next] bridge: Implement MLD Querier wake-up calls / Android bug workaround
Date: Mon, 17 Aug 2020 10:39:00 +0200 [thread overview]
Message-ID: <87zh6t650b.fsf@miraculix.mork.no> (raw)
In-Reply-To: <20200816202424.3526-1-linus.luessing@c0d3.blue> ("Linus =?utf-8?Q?L=C3=BCssing=22's?= message of "Sun, 16 Aug 2020 22:24:24 +0200")
Linus Lüssing <linus.luessing@c0d3.blue> writes:
> Currently there are mobile devices (e.g. Android) which are not able
> to receive and respond to MLD Queries reliably because the Wifi driver
> filters a lot of ICMPv6 when the device is asleep - including
> MLD. This in turn breaks IPv6 communication when MLD Snooping is
> enabled. However there is one ICMPv6 type which is allowed to pass and
> which can be used to wake up the mobile device: ICMPv6 Echo Requests.
This is not a bug. They are deliberately breaking IPv6 because they
consider this a feature. You should not try to work around such issues.
It is a fight you cannot win. Any workaround will only encourage them
to come up with new ways to break IPv6.
Bjørn
next prev parent reply other threads:[~2020-08-17 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 20:24 [RFC PATCH net-next] bridge: Implement MLD Querier wake-up calls / Android bug workaround Linus Lüssing
2020-08-16 22:08 ` [Bridge] " Stephen Hemminger
2020-08-16 22:10 ` David Miller
2020-08-23 15:42 ` Linus Lüssing
2020-08-23 17:19 ` Stephen Hemminger
2020-08-23 19:49 ` Felix Fietkau
2020-08-17 4:10 ` David Miller
2020-08-17 8:39 ` Bjørn Mork [this message]
2020-08-17 13:17 ` [gluon] " Sven Eckelmann
2020-08-17 13:35 ` Bjørn Mork
2020-08-17 14:24 ` Daniel Golle
2020-08-18 0:35 ` [bridge] fdde3c8b90: WARNING:at_net/core/rtnetlink.c:#rtnl_link_register kernel test robot
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=87zh6t650b.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gluon@luebeck.freifunk.net \
--cc=linus.luessing@c0d3.blue \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=openwrt-devel@lists.openwrt.org \
--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).