Some firewalls (like sonicwall enhanced) can slow down acks to traffic shape inbound traffic. It's not perfect, but it's often better than nothing. Most business-class ISP's should offer QOS in both directions. We certainly do for our T-1 or better customers. (sorry, I meant this to be a reply all) On Sat, Feb 4, 2012 at 8:57 PM, George B. wrote: > On Sat, Feb 4, 2012 at 4:43 PM, Jonathan Morton > wrote: > > > There are two good things you can do. > > > > 1) Pressure your ISP to implement managed queueing and ECN at the > head-end device, eg. DSLAM or cell-tower, and preferably at other > vulnerable points in their network too. > > Well, if they have a Cisco network, that might work. Few other > network gear vendors actively support ECN. > > > 2) Implement TCP *receive* window management. This prevents the TCP > algorithm on the sending side from attempting to find the size of the > queues in the network. Search the list archives for "Blackpool" to see my > take on this technique in the form of a kernel patch. More sophisticated > algorithms are doubtless possible. > > Probably not something I want to use in production. > > Thanks, Johnathan. Now yet another question: > > Two different server configurations (these are real life examples, by the > way): > > 1. eth0 and eth1 bound as bond0 with vlans hanging off of them. > Where to put the qdisc? On the bond interface? On the Ethernet > interfaces? On the vlan interfaces? > > 2. eth0 and eth1 have vlan interfaces attached as eth0.10, eth1.10 > and eth0.20, eth1.20. Those are bound to bond interfaces, bond10 and > bond20. Same question, where best to apply the qdisc. > > George > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > -- “The world is not comprehensible, but it is embraceable.”