From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 129BA21F0EF for ; Sun, 19 Aug 2012 05:08:13 -0700 (PDT) Received: by obqv19 with SMTP id v19so19626807obq.16 for ; Sun, 19 Aug 2012 05:08:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=jSAW9ynSjM5P4UaTE/uI7QtrctFFfNRjYRJkQkj0vuI=; b=PaBu/I1tyfWGmewEols6qzictnaZFDtqHPMMPo4Kmw0l2x8n59F+Ba+8nYd5ppdZdB ZywE0oHqFXJfPMmfvEldD8hrFXq/kwWu02Th54azbQNfH+t9DMDjx36vF50uRPJc3+Rp brGk/gmSYqZOE2HvQwTwsemL3PPsrK/qLAg122DNEq/frnvkR4/qGAwioNgZLaMA1Wn2 UOkpGE2G3GNT8KZINJto9vTHKi+JfZpO3G8q2s+zgHYtX60oYZpXJD3rhdJMXqE0NtX/ +x2/pfqtV/gZiGc1hgz6PbthYerYo+NU0C2RRisXB1QRKATUvdoVK3ydtnUJZbf1NhvB zq8g== MIME-Version: 1.0 Received: by 10.50.85.166 with SMTP id i6mr6785828igz.71.1345378092505; Sun, 19 Aug 2012 05:08:12 -0700 (PDT) Received: by 10.64.77.198 with HTTP; Sun, 19 Aug 2012 05:08:12 -0700 (PDT) X-Originating-IP: [2001:470:71:c8:ed6d:fc1a:efba:d0c7] In-Reply-To: References: <502F72D2.1080704@googlemail.com> Date: Sun, 19 Aug 2012 14:08:12 +0200 Message-ID: From: Maciej Soltysiak To: Dave Taht Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnD3RzbDrgVAVSiSXk43BnrJItdNfXX7nZ89Y9KL0hZ5fshM4xtppih7ok1+qhUnKY+Kwl8 Cc: cerowrt-users@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] [Cerowrt-users] Cerowrt_question X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2012 12:08:14 -0000 On Sat, Aug 18, 2012 at 7:57 PM, Dave Taht wrote: > On Sat, Aug 18, 2012 at 3:47 AM, Oliver Niesner > 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