General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] tc -s qdisc questions
Date: Fri, 15 May 2015 09:45:10 -0700	[thread overview]
Message-ID: <CAA93jw4n10Y2QHyvRoEH-7_oVrbh1yuPCiBvGxykh=E1pt9w9g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1505151055211.9487@uplift.swm.pp.se>

On Fri, May 15, 2015 at 1:55 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Fri, 15 May 2015, Kevin Darbyshire-Bryant wrote:
>
>> Ahh!  Penny drops, light goes on.  Thanks Jonathan & Dave.  I thought it
>> was some magic the router performed but now I can see how silly my thinking
>> is on that.  So presumably it would be helpful to enable ecn on the openwrt
>> router box IF that box were producing significant traffic of its own, in
>> addition to all the LAN side boxes?
>
>
> Correct. If it for instance was running a http proxy server (and thus
> terminating TCP sessions), turning on ECN on the box itself would make
> sense.

This was (prior to crypto on everything http starting to be mandated) a
very good idea for satellite links - run everything through a proxy, make
the proxy and proxy box be smarter about tcp/ecn - and set the fq_codel
implementation more appropriately for the rtt.

Web proxies are still quite  heavily used in education and some corporate
markets. In fact the first ever commercially deployed fq_codel implementation
(in NZ) was on a web proxy/firewall box.

I do wish more high end firewall makers were paying attention to the
bufferbloat work. They are usually the first line of defense and sole
hop before hitting the (cable,dsl,fiber)modem and thus are perfect
targets for deploying aqm/fq technologies.

Certainly the pfsense
folk are getting it but no sign of life at barracuda and checkpoint
that I know of.


> --
> Mikael Abrahamsson    email: swmike@swm.pp.se



-- 
Dave Täht
Open Networking needs **Open Source Hardware**

https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67

  reply	other threads:[~2015-05-15 16:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 22:22 Kevin Darbyshire-Bryant
2015-05-14 23:37 ` Jonathan Morton
2015-05-14 23:41 ` Dave Taht
2015-05-15  8:16   ` Kevin Darbyshire-Bryant
2015-05-15  8:55     ` Mikael Abrahamsson
2015-05-15 16:45       ` Dave Taht [this message]
2015-05-17 20:23       ` Kevin Darbyshire-Bryant
2015-05-18  5:46         ` Mikael Abrahamsson
2015-05-18  8:09           ` Kevin Darbyshire-Bryant

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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='CAA93jw4n10Y2QHyvRoEH-7_oVrbh1yuPCiBvGxykh=E1pt9w9g@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /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