From: jb <justin@dslr.net>
To: David Lang <david@lang.hm>
Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat at high edge rates
Date: Wed, 16 Nov 2016 15:09:21 +1100 [thread overview]
Message-ID: <CAH3Ss948=ceqbbEVbC-dJ+ZjhXgwXsaFPzBuepy8BYZxA7YW0w@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.75.62.1611151633250.9765@qynat-yncgbc>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
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: 1984 bytes --]
next prev parent reply other threads:[~2016-11-16 4:10 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 [this message]
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
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='CAH3Ss948=ceqbbEVbC-dJ+ZjhXgwXsaFPzBuepy8BYZxA7YW0w@mail.gmail.com' \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=david@lang.hm \
/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