Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Richard Smith <smithbone@gmail.com>
To: David Lang <david@lang.hm>, Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] the 3 focus problems we have
Date: Thu, 19 Mar 2015 12:01:46 -0400	[thread overview]
Message-ID: <550AF2EA.9010509@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1503161042380.32001@nftneq.ynat.uz>

On 03/16/2015 01:49 PM, David Lang wrote:
> On Mon, 16 Mar 2015, Dave Taht wrote:
>
>> On Mon, Mar 16, 2015 at 10:34 AM, David Lang <david@lang.hm> wrote:
>>
>>> On Mon, 16 Mar 2015, Dave Taht wrote:
>>>
>>>  1) We need a new box that can do inbound shaping at up to 300mbit.
>>> So far
>>>> that box has not appeared. We have not explored policing as an
>>>> alternative.
>>>>
>>>
>>> If you are using a x86 processor, how much cpu does this take?
>>
>>
>> diddly.
>
> this isn't sold as an AP, it's a bit pricy, but not insanely expensive
> ($200-250 depending on options)
>
> 1GHz dual core AMD cpu, 4G  1066RAM 2 mini PCIe 3xGid-E

I'm currently running the following as the Gateway/DNS/DHCP for the mid 
level startup (40 people) I work for.

http://www.newegg.com/Product/Product.aspx?Item=N82E16856205007

I added 4gigs of ram and the cheapest SSD I could find.

It does inbound/outbound shaping on our 100/15Mbit link and when I slam 
the link with netperf-wrapper top tells me the cpu is about 30% used.

I don't have any log files but when I tested this box in-line on a GigE 
network I seem to remember it being able to do far above 100Mbit but I 
don't remember how much more.

It's running a custom build of BB.  Custom because the dual GigE network 
chipset is not recognised by by openwrt BB and I had make a small patch 
to fix that but every thing else is stock BB.  QOS is qos-scripts 
scripts and not a version of sqm-scripts.  When I got it all going I 
didn't full recognize that all the sqm stuff was not in qos-scripts.  It 
works and currently meets our needs so I've not felt much need to mess 
with it.

It has a PCI-E x1 slot so you could add a wireless adapter.

Sadly its out of stock now but there are probably plenty more options if 
we started looking for them.

-- 
Richard A. Smith

  reply	other threads:[~2015-03-19 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 17:01 Dave Taht
2015-03-16 17:34 ` David Lang
2015-03-16 17:35   ` Dave Taht
2015-03-16 17:49     ` David Lang
2015-03-19 16:01       ` Richard Smith [this message]
2015-03-19 19:32         ` Aaron Wood
2015-03-19 20:15           ` 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/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=550AF2EA.9010509@gmail.com \
    --to=smithbone@gmail.com \
    --cc=cerowrt-devel@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