From: jb <justin@dslr.net>
To: Colin Dearborn <Colin.Dearborn@sjrb.ca>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat at high edge rates
Date: Thu, 17 Nov 2016 11:16:27 +1100 [thread overview]
Message-ID: <CAH3Ss96mHbLjxNSZQcAkgZg+ptNv8jT_cBiJugctT=dLzcLC5Q@mail.gmail.com> (raw)
In-Reply-To: <CY4PR04MB05665A2EFEB8CE55866C839A95BE0@CY4PR04MB0566.namprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2448 bytes --]
Apparently there is not enough duration currently: there is actual buffer
bloat data in your results, but it is insufficient in quantity so the site
isn't bothering to show and interpret it. Can you try one run by extending
the duration of download and upload phases?
if that doesn't work I'll have to patch the binary to make sure there is
always enough, and upload a new one..
thanks
On Thu, Nov 17, 2016 at 7:54 AM, Colin Dearborn <Colin.Dearborn@sjrb.ca>
wrote:
> I just ran it on ubuntu 16.04.1 LTS, as root, and it did not store the
> bufferbloat, quality or speed grades.
>
> https://www.dslreports.com/speedtest/6186501
>
> https://www.dslreports.com/speedtest/6186425
>
>
>
> I do note that it ran these tests over my HE.net tunnel and there doesn’t
> seem to be an easy way to choose IPv6 vs IPv4 on the command line.
>
> Disabling the IPv6 tunnel, I still don’t see the grades:
>
> https://www.dslreports.com/speedtest/6187015
>
>
>
> ./dslrcli-linux-amd64 --version
>
> Dslrcli version 0.1 - 17-Nov-2016
>
>
>
> *From:* Bloat [mailto:bloat-bounces@lists.bufferbloat.net] *On Behalf Of *
> jb
> *Sent:* Tuesday, November 15, 2016 9:09 PM
> *To:* David Lang <david@lang.hm>
> *Cc:* bloat <bloat@lists.bufferbloat.net>
> *Subject:* Re: [Bloat] bufferbloat at high edge rates
>
>
>
> It has to run as root / Admin in order to do ICMP in order to test buffer
> bloat.
>
>
>
> If you run it under a non privileged user account it cannot get permission
> for ICMP, so although it locates the nearest servers using http ping, it
> isn't doing any buffer bloat testing.
>
>
>
> I'm not sure that is the issue but that's the first thing that comes to
> mind..
>
>
>
>
>
> On Wed, Nov 16, 2016 at 11:34 AM, David Lang <david@lang.hm> wrote:
>
> On Tue, 15 Nov 2016, jb wrote:
>
> The command line tool is available to anyone now (Windows, OSX and linux),
> it does buffer bloat probing, using ICMP if run as root, and is immune to
> any browser issues. It can be downloaded here from the sticky:
> http://www.dslreports.com/forum/speedtestbinary
>
>
> This does not seem to be reporting any bloat info (I've run it a couple
> times)
>
> http://www.dslreports.com/speedtest/6156013
>
> David Lang
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
>
[-- Attachment #2: Type: text/html, Size: 6302 bytes --]
next prev parent reply other threads:[~2016-11-17 0:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 19:02 Dave Taht
2016-11-14 20:06 ` Kathleen Nichols
2016-11-15 16:22 ` Dave Taht
2016-11-15 23:16 ` jb
2016-11-15 0:11 ` jb
2016-11-15 0:31 ` Dave Taht
2016-11-15 0:36 ` Jonathan Morton
2016-11-15 15:23 ` James Cloos
2016-11-15 15:43 ` Jan Ceuleers
2016-11-16 0:34 ` David Lang
2016-11-16 4:09 ` jb
2016-11-16 6:00 ` Stefan Alfredsson
2016-11-16 11:26 ` Stefan Alfredsson
2016-11-16 20:27 ` jb
2016-11-16 6:02 ` David Lang
[not found] ` <CY4PR04MB05665A2EFEB8CE55866C839A95BE0@CY4PR04MB0566.namprd04.prod.outlook.com>
2016-11-17 0:16 ` jb [this message]
2016-11-17 7:50 ` David Lang
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='CAH3Ss96mHbLjxNSZQcAkgZg+ptNv8jT_cBiJugctT=dLzcLC5Q@mail.gmail.com' \
--to=justin@dslr.net \
--cc=Colin.Dearborn@sjrb.ca \
--cc=bloat@lists.bufferbloat.net \
/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