Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Collin Anderson <cmawebsite@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] hardware suggestions?
Date: Mon, 26 Aug 2013 20:44:29 -0400	[thread overview]
Message-ID: <CAFO84S6YBHYVSyj3XLNchh5caRMPXe=q0R7zB_WPfbnvGEOt6Q@mail.gmail.com> (raw)

Hi All,

After 5 years of knowingly suffering from high latency from uploads
through Comcast, I have finally discovered the term "bufferbloat" and
am glad to see that at least some people are pushing for better
queuing algorithms. I use ssh all day for making websites at work and
would like to eliminate, or at least reduce latency from buffer bloat.

What hardware should I buy? Netgear WNDR3800? I want to buy the same
hardware as you all so when I find repeatable bugs I can complain and
you can reproduce them. :) I want something reliable and easy to get
set up and configure.

Also, if you want to get some data and find bugs with CeroWRT, it
would be cool if I could just install it and check a "send statistics
and crash reports" box. I'm not much of a kernel hacker myself. I
mostly stick with making websites with python. If I'm not helping to
improve CeroWRT, I might as well use OpenWRT if it has decent AQM and
is a little more reliable.

Thanks,
Collin

             reply	other threads:[~2013-08-27  0:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  0:44 Collin Anderson [this message]
2013-08-28 12:00 ` Juergen Botz
2013-08-28 18:44 ` Dave Taht
2013-08-29 13:18   ` Luke Hamburg
2013-08-30 18:17   ` Michael Richardson

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='CAFO84S6YBHYVSyj3XLNchh5caRMPXe=q0R7zB_WPfbnvGEOt6Q@mail.gmail.com' \
    --to=cmawebsite@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