Historic archive of defunct list cerowrt-users@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-users@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-users] Cerowrt_question
Date: Sun, 19 Aug 2012 14:08:12 +0200	[thread overview]
Message-ID: <CAMZR1YBFr3t_+mUDCLYWrjyPdSVHxcRSn6cY-vsuMo6usGw90A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7MR_0XpUB=ZxC52pkjuHGYayqQerc+w+VMHDuc4nu0NA@mail.gmail.com>

On Sat, Aug 18, 2012 at 7:57 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Sat, Aug 18, 2012 at 3:47 AM, Oliver Niesner
> <oliver.niesner@gmail.com> wrote:
>> But at this point i have some problems with understanding: I run the cerowrt
>> as a second router in my
>> normal network, so the gateway to the internet is my "normal" router with
>> all the problems with buffers we all have. How could it be that the
>> buffersizes are so much better even when i connected with my
>> standard router??
>
> The point here is that by setting qos on and doing rate limiting
> you've moved the core bottleneck from the gateway device or other main
> router to cero, which can then manage the problem.
>
> (but only for devices that are behind it. And, yes, if you have
> competing traffic on the main router, it will mess up qos)
>
> I generally advise people to FIRST make sure their environment still
> works - like printing, samba, dlna, and other services - before making
> a version of cerowrt into their main router. Particularly if they have
> spouses/kids/work dependent on the network always working.
I have the same setup as you, Oliver, a EPC3925 cable modem with
WNDR3800 connected to it as second device so I am able to fight
buffers where I have access.

What I started doing last week though is I deployed an additional
WRT54GL for emergency, including family use if I make WNDR3800
inoperable. I connect it to the cisco cable modem. For the WRT54GL I
am using Hector Ordorica's Tomato RAF build with some anti-bufferbloat
changes, for the broadcom chip buffer size, txqueuelen and around qos:
http://ordorica.org/blog/tomato-firmware-wreduced-bufferbloat

Hector is not doing any further builds, but it gives very good results
on netalyzr.

This allows me to tinker away with WNDR3800 and if I break anything,
anyone can still use the WRT54GL.
Yes, this means I can have competeng traffic on the router, but the
54GL is for emergency use only.

Regards,
Maciej

      reply	other threads:[~2012-08-19 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18 10:47 Oliver Niesner
2012-08-18 17:57 ` Dave Taht
2012-08-19 12:08   ` Maciej Soltysiak [this message]

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

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

  git send-email \
    --in-reply-to=CAMZR1YBFr3t_+mUDCLYWrjyPdSVHxcRSn6cY-vsuMo6usGw90A@mail.gmail.com \
    --to=maciej@soltysiak.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt-users@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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