Just make sure it has enough flow capacity for your deployment case. The problem with all of these solutions is the are flow (or context) limited. Understand the edges and make sure you instrument for them.
Neil. Sent from my iPhone On 7 Jul 2016, at 09:04, Martin Hepworth <max...@gmail.com<mailto:max...@gmail.com>> wrote: Bluecoat's PacketShaper is really good - not use it for a long time (since Packetshaper got bought) but the effects are just stunning. https://www.bluecoat.com/products-and-solutions/wan-optimization-packetshaper worth a look /pricing -- Martin Hepworth, CISSP Oxford, UK On 7 July 2016 at 08:49, Brian Candler <b.cand...@pobox.com<mailto:b.cand...@pobox.com>> wrote: On 06/07/2016 22:20, Iain Grant wrote: Modifying the window size is not new, shorewall can do it - anything that can use the ifb driver in linux can! Can you point me to some documentation to back up that assertion? As I understand it, etinc and packeteer work by modulating the TCP receive window size. I can't find anything about ifb that says it can work that way. It says it does "policing" (i.e. dropping packets out of profile) and "shaping" (i.e. delaying packets in a queue). You can have "active queue management" using the FQ_CODEL algorithm, which stops your queues getting too full so that latency is reasonable, but as far as I can see it still basically just drops packets, or marks them with ECN flags, as a way of signalling the TCP sender to slow down.
