From: Dave Taht <dave.taht@gmail.com>
To: David Reed <dpreed@reed.com>
Cc: moeller0 <moeller0@gmx.de>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] odroid C1+ status
Date: Sun, 6 Mar 2016 07:57:28 -0800 [thread overview]
Message-ID: <CAA93jw42uhYie7sB5PeEzLnp3iGHgq6UfVJ2ePHK=PUyh4twgw@mail.gmail.com> (raw)
In-Reply-To: <1457216372.19224891@apps.rackspace.com>
On Sat, Mar 5, 2016 at 2:19 PM, <dpreed@reed.com> wrote:
> I have a Banana Pi, but I can't imagine why it would be useful as a router.
The banana pi is being used as the test generator in the comcast
bufferbloat test program.
> Why would Comcast even bother? A Raspberry Pi 3 would be better, and far more available. (though I think the slow Ethernet port and low end WiFi on the Raspberry Pi 3 would make it sort of marginal, it's certainly quite fine for a low-end OpenWRT machine if you want to live at 50 Mb/sec)
What I had tried to do several times over the past years is have a
little monitoring box I could put out along the edges of the yurtlab
network, doing mrtg, smokeping, traceroute, and acting as a
netperf/iperf server. I'd ultimately settled on the beaglebone blacks
for this, but never got to where they would stay up long enough to be
useful.
next prev parent reply other threads:[~2016-03-06 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 20:23 Dave Taht
2016-03-05 22:19 ` dpreed
2016-03-06 15:57 ` Dave Taht [this message]
2016-03-07 21:25 ` Mikael Abrahamsson
2016-03-05 22:21 ` David Lang
2016-03-05 23:34 ` Luis E. Garcia
2016-03-05 23:41 ` John Yates
2016-03-06 14:27 ` James Cloos
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='CAA93jw42uhYie7sB5PeEzLnp3iGHgq6UfVJ2ePHK=PUyh4twgw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
--cc=moeller0@gmx.de \
/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