Full integration between traffic shaper and Squid3
Most people around me uses Pfsense for its traffic shaper. Unfortunetely traffic shaper applies to Squid3 package too.
Traffic shaper also tries to shape cache hits. Which kills the whole purpose of caching (speed). I saw some workarounds for squid2 but I want full integration between traffic shaper and squid3
Ok I put in $100 on this.
I'm surprised noone shows any interest for this. Am I missing something?
At the high level, traffic shaping is applied at the connection level, before you even reach Squid. The only way I can think of to make it work correctly is like you said, "integrate Squid" into the traffic shaper in the kernel.
A work around could be to place a traffic rule that puts a connection into an "unlimited" speed queue if the connection is destined to Squids IP+port.
marcelloc last edited by
I saw some workarounds for squid2 but I want full integration between traffic shaper and squid3
If it's still open, send me squid2 workaround so I can try to merge it on squid3 package.