From: Colin Dearborn <Colin.Dearborn@sjrb.ca>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
Rich Brown <richb.hanover@gmail.com>
Cc: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] new public web tests for bufferbloat
Date: Thu, 2 Jun 2016 20:05:29 +0000 [thread overview]
Message-ID: <CO2PR04MB227741A4EAEEEC51D05EC8D995580@CO2PR04MB2277.namprd04.prod.outlook.com> (raw)
In-Reply-To: <7ioa7jv2pb.wl-jch@pps.univ-paris-diderot.fr>
Plenty of easy ways to do v4 and v6.
DNS can be built to only have hosts for v4 or v6, and you run two tests, one to each set of hosts.
Comcast has been doing it forever.
http://speedtest.xfinity.com/ (they use speedtest.net's code, and they have it skinned).
-----Original Message-----
From: Bloat [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of Juliusz Chroboczek
Sent: Thursday, June 02, 2016 12:57 PM
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] new public web tests for bufferbloat
> TL;DR - they seem to have all the elements in place to measure the
> latency during transfers. If they fix some of these problems, they'll
> have a winner.
No easy way to do both v4 and v6 tests -- you need to manually remove your
IPv6 default route in order to test v4.
-- Juliusz
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2016-06-02 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1112.1464880746.3642.bloat@lists.bufferbloat.net>
2016-06-02 16:54 ` Rich Brown
2016-06-02 18:57 ` Juliusz Chroboczek
2016-06-02 20:05 ` Colin Dearborn [this message]
2016-06-02 22:26 ` Kathleen Nichols
2016-06-01 16:55 Dave Taht
2016-06-01 22:58 ` Alan Jenkins
2016-06-01 23:02 ` Alan Jenkins
2016-06-01 23:06 ` Alan Jenkins
2016-06-02 0:58 ` Dave Taht
[not found] ` <CAA93jw7hqkDBbRY4sSJEoACGGs6kmsntHSDzqQzbZW+oRsgcrw@mail.gmail.com>
2016-06-02 15:19 ` Alan Jenkins
2016-06-02 8:31 ` moeller0
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=CO2PR04MB227741A4EAEEEC51D05EC8D995580@CO2PR04MB2277.namprd04.prod.outlook.com \
--to=colin.dearborn@sjrb.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=jch@pps.univ-paris-diderot.fr \
--cc=richb.hanover@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