From: jb <justin@dslr.net>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Adblock - or another extension - is incorrectly blocking the speed test
Date: Mon, 27 Apr 2015 01:15:15 +1000 [thread overview]
Message-ID: <CAH3Ss94U29O7xTXi0i4gA+Da2t-8ma=Pgvc=ULy3wJdgf5Z=vA@mail.gmail.com> (raw)
In-Reply-To: <20150426142336.GA24211@sesse.net>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
If they are using NAT64, they can use an ipv6 speed test, natively, no ?
"In general, NAT64 is designed to be used when the communication
is initiated by IPv6 hosts."
On Mon, Apr 27, 2015 at 12:23 AM, Steinar H. Gunderson <
sgunderson@bigfoot.com> wrote:
> On Mon, Apr 27, 2015 at 12:00:31AM +1000, jb wrote:
> > No, I'm not going to do that. I absolutely hate even _considering_
> changing
> > how I want to do something for an extension that doesn't know the
> difference
> > between an IP address and a script.
>
> What about if the user is behind NAT64? IP literals won't work at all in
> that
> case.
>
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 1857 bytes --]
next prev parent reply other threads:[~2015-04-26 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 5:38 Jan Ceuleers
2015-04-25 11:44 ` jb
2015-04-25 14:15 ` Jan Ceuleers
2015-04-26 4:17 ` jb
2015-04-26 6:26 ` Jan Ceuleers
2015-04-26 14:00 ` jb
2015-04-26 14:23 ` Steinar H. Gunderson
2015-04-26 15:15 ` jb [this message]
[not found] ` <20150426152719.GB24211@sesse.net>
2015-04-26 15:42 ` jb
2015-04-26 15:35 ` David Lang
2015-04-26 16:30 ` Steinar H. Gunderson
2015-04-26 14:17 ` jb
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH3Ss94U29O7xTXi0i4gA+Da2t-8ma=Pgvc=ULy3wJdgf5Z=vA@mail.gmail.com' \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.net \
--cc=sgunderson@bigfoot.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