[prev in list] [next in list] [prev in thread] [next in thread] 

List:       squid-users
Subject:    Re: [squid-users] qos_flow.
From:       Amos Jeffries <squid3 () treenet ! co ! nz>
Date:       2014-03-27 2:15:30
Message-ID: 533389C2.5090903 () treenet ! co ! nz
[Download RAW message or body]

On 27/03/2014 9:45 a.m., Beto Moreno wrote:
> On Mon, Mar 24, 2014 at 7:00 PM, Amos Jeffries <squid3@treenet.co.nz> wrote:
>> On 25/03/2014 1:26 p.m., Beto Moreno wrote:
>>> Hi.
>>>
>>> Trying to understand squid qos_flows feature, I had been reading a
>>> lot, but hadn't found any specific info/howto  with clarify examples.
>>>
>>> How can I use qos_flows in my fw?
>>>
>>
>> qos_flows tag the packets delivered to clients containing HTTP responses.
>> Squid 3.2 and later can label them with TOS/DiffServ (for
>> between-machine labelling) or Linux MARK (for within-machine labelling).
>> Older Squid are limited to TOS values.
>>
>> http://www.squid-cache.org/Doc/config/qos_flows/
>> http://wiki.squid-cache.org/Features/QualityOfService
>>
>>> I had try delay_pools, now I want to learn this other feature.
>>>
>>> Anyone with a example for a noob willl be appreciated.
>>>
>>> Working with squid 3.1.x, thanks.
>>>
>>
>> 3.1 can do most of what is documented, but is limited to TOS values and
>> without the preserve-miss and miss=X functionality.
>>
>> Amos
> 
>   Sorry Amos, I still don't understand this, this is totally new for
> me, still reading to see how to use this feature.
>   Once I setup squid example with;
> 
> qos_flows local-hit=0x30
> 
>   What is going to happen?
> 

The packets returned by Squid to the client for all responses logged as
TCP_HIT or TCP_MEM_HIT etc should be marked with TOS value 0x30.

Amos

[prev in list] [next in list] [prev in thread] [next in thread]