Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Sven Eckelmann <sven@narfation.org>
Cc: gluon@luebeck.freifunk.net,
	"Linus Lüssing" <linus.luessing@c0d3.blue>,
	"Nikolay Aleksandrov" <nikolay@cumulusnetworks.com>,
	netdev@vger.kernel.org,
	"Roopa Prabhu" <roopa@cumulusnetworks.com>,
	bridge@lists.linux-foundation.org,
	openwrt-devel@lists.openwrt.org,
	"David S . Miller" <davem@davemloft.net>
Subject: Re: [gluon] Re: [RFC PATCH net-next] bridge: Implement MLD Querier wake-up calls / Android bug workaround
Date: Mon, 17 Aug 2020 15:35:38 +0200	[thread overview]
Message-ID: <87blj95r9x.fsf@miraculix.mork.no> (raw)
In-Reply-To: <1830568.o5y0iYavLQ@sven-edge> (Sven Eckelmann's message of "Mon, 17 Aug 2020 15:17:37 +0200")

Sven Eckelmann <sven@narfation.org> writes:
> On Monday, 17 August 2020 10:39:00 CEST Bjørn Mork wrote:
>> Linus Lüssing <linus.luessing@c0d3.blue> writes:
> [...]
>> 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.
>
> Who are "they" and

Google.

> where is this information coming from?

I made it up.

> And what do they gain from breaking IPv6?

Battery time.

> Wouldn't it be easier for them just to disable IPv6 
> than adding random looking bugs?

You would think so.

If it isn't clear, I am hoping to provoke them to re-classify the
"feature" as a bug and fix it.  That's what it takes to prove I am wrong.
Should be easy-peasy.



Bjørn

  reply	other threads:[~2020-08-17 13:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-16 20:24 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
2020-08-17 13:17   ` [gluon] " Sven Eckelmann
2020-08-17 13:35     ` Bjørn Mork [this message]
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=87blj95r9x.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 \
    --cc=sven@narfation.org \
    --subject='Re: [gluon] Re: [RFC PATCH net-next] bridge: Implement MLD Querier wake-up calls / Android bug workaround' \
    /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

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).