Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: wndr3800 replacement
Date: Fri, 28 Mar 2014 12:39:19 -0700	[thread overview]
Message-ID: <CAA93jw6nOjGbL8ZdqV4s_9T=7hw7dg_8t+6S8KjenjsXVEHX4A@mail.gmail.com> (raw)
In-Reply-To: <30456.1396032043@sandelman.ca>

On Fri, Mar 28, 2014 at 11:40 AM, Michael Richardson <mcr@sandelman.ca> wrote:
>
> Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>     > I also think that it'll be very hard to find a box that is decently
>     > priced
>     > that also will do gig speeds *and* will do AQM, since most home
>     > gateways that
>
> So, I'm struggling to get a $700 Cisco (not Linksys) SOHO switch to forward
> packets at GbE across my home LAN.   Gigabit ethernet in the home is actually
> a reality.... and having a Gigabit LAN hit a 11Mb/s (half-duplex!) 802.11b
> wireless means that in many homes, we actually need a box that satisfies
> both.
>
> My vote would be to double the price from $80 to $250, and set that as the
> new base for cerowrt work.  If it can't forward more than 2-3 GbE links,
> that is just fine.  I don't expect 24-ports of GbE.
> (I was expecting that cisco switch to do that... sadly no lost packets
> on a $100 unmanaged FE switch...)

 I started looking at the edgerouter LTE and related boxes again.

Does anyone else have one?

They have a new release based on 3.4 out; backporting fq_codel might work.

I don't have any numbers on it's performance however, and it does look like
updating it to 3.10 would be good idea.

>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>
>
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2014-03-28 19:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.02.1403251259390.747@uplift.swm.pp.se>
2014-03-25 15:16 ` Dave Taht
2014-03-26 22:11   ` David Lang
2014-03-27 12:50     ` Aaron Wood
2014-03-27 14:39       ` David Lang
2014-03-28  8:36         ` Mikael Abrahamsson
2014-03-28  9:33           ` Sebastian Moeller
2014-03-28 13:30           ` Aaron Wood
2014-03-28 18:40           ` Michael Richardson
2014-03-28 19:39             ` Dave Taht [this message]
2014-03-28 21:01               ` Aaron Wood
2014-03-29 21:08               ` Michael Richardson
2014-03-29 21:25                 ` Dave Taht
2014-03-30 22:03                   ` Michael Richardson
2014-03-30 22:10                     ` Dave Taht
2014-03-28 19:14           ` Michael Richardson
2014-03-29 19:27 Martin Bailey
2014-03-29 19:52 ` Dave Taht
2014-03-29 19:56 ` Dave Taht
2014-03-29 20:19   ` Martin Bailey

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='CAA93jw6nOjGbL8ZdqV4s_9T=7hw7dg_8t+6S8KjenjsXVEHX4A@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=mcr@sandelman.ca \
    /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