Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Noah Causin <n0manletter@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] netperf.bufferbloat.net
Date: Tue, 13 Dec 2016 20:56:14 -0500	[thread overview]
Message-ID: <0d1ae038-3ed4-4b66-daca-f5b1b0a4bd72@gmail.com> (raw)
In-Reply-To: <20161214003745.AB38F202@taggart.lackof.org>

There is flent-freemont.bufferbloat.net

(California).


On 12/13/2016 7:37 PM, Matt Taggart wrote:
> Hi Cerowrt-devel (and mostly Rich),
>
> I was running some betterspeedtest.sh today using the default
> netperf.bufferbloat.net server (aka atl.richb-hanover.com) and only getting
> about 2mbit down and 5mbit up (at home, Comcast in Seattle). The broadband
> reports speedtest gives me 30mbit down/6mbit up (which is the level of
> comcast I have).
>
> Am I bottlenecked somewhere? Is there another server closer to Seattle I
> should be using?
>
> Thanks,
>


  reply	other threads:[~2016-12-14  1:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14  0:37 Matt Taggart
2016-12-14  1:56 ` Noah Causin [this message]
2016-12-14  4:25   ` Matt Taggart
2016-12-14 18:44 Rich Brown

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0d1ae038-3ed4-4b66-daca-f5b1b0a4bd72@gmail.com \
    --to=n0manletter@gmail.com \
    --cc=cerowrt-devel@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