Re: Fwd: Re: [squid-users] Re: Bandwidth split?

On Wed, 10 Nov 2010 14:15:45 +0100, "J Webster" <webster_jack_at_hotmail.com>
wrote:
> 256/8 and then * 100 is what I have been doing I think.
> Ideally, I need an unlimited server bucket but all the ncsa users to
have
> 512kbps to 1Mbps individually.
> For example, 60 users connected and they all have 1Mbps max. The server
is
> 100Mbit.
>

... both of these regex pattern sets are catching a HUGE amount of things
more than you expect.

> Current conf as per previous emails:
> acl magic_words1 url_regex -i 192.168

  10.0.192.168 or 10.192.168.0 or 192.168.0.0 style raw-IPs being
accessed?
  or URL containing IPs coded in the path somewhere
(http://example.com/foo/192/168)?

It seems like you are wanting a dstdom_regex ACL type at least.

From your description of this as an "unlimited server" it seems more like
you actually want a src ACL to match traffic coming from the server. To
match traffic going *to* the server it would need to be dstdomain (fast) or
dst (slow with a match http_access check required).

> acl magic_words2 url_regex -i ftp .exe .mp3 .vqf .tar.gz .gz .rpm .zip
> .rar
> .avi .mpeg .mpe .mpg .qt .ram .rm .iso .raw .wav .mov

I suspect the "ftp" entry in this second one should instead be:
  acl FTP proto FTP

the if the others are supposed to match files they definitely need
location anchors and urlpath_regex ACL type.
  ie \.foo(\?.*)?$

To catch video media files being downloaded directly the pattern looks
like this:
  urlpath_regex -i \.(mov|mpe|mpe?g|avi|divx?|qt|ra?m)(\?.*)?$

add other file extensions into the (|) list as needed.

> # Added nsca_users in a boolean AND fashion
> delay_pools 3
> delay_class 1 2
> delay_parameters 1 -1/-1 -1/-1
> delay_access 1 allow ncsa_users magic_words1
> delay_access 1 deny all

For non-limited like this it is more efficient to simply not pool the
relevant machines/requests.

Add "!magic_words1" to the other delay_access allow rules.

> delay_class 2 2
> #delay_parameters 2 5000/150000 5000/120000
> delay_parameters 2 32000/150000 32000/120000
> delay_access 2 allow ncsa_users magic_words2
> delay_access 2 deny all
> delay_class 3 1
> # 512Kbit/s fill rate, 1024 Kbit/s reserve
> delay_parameters 3 64000/128000
> delay_access 3 allow ncsa_users
> delay_access 3 deny all
>
> --------------------------------------------------
> From: "Amos Jeffries"
>
>> On 10/11/10 05:45, J Webster wrote:
>>> Thanks for the help.
>>> Does anyone know the difference between fill rate and reserve in how
>>> they are applied to restrciting proxy bandwidth?
>>>> # 256 Kbit/s fill rate, 1024 Kbit/s reserve
>>>
>>
>> Firstly it is measured in BYTE/sec. So alter you numbers by 8 for
>> squid.conf
>>
>> http://wiki.squid-cache.org/Features/DelayPools
>>
>> Amos
>> --
>> Please be using
>> Current Stable Squid 2.7.STABLE9 or 3.1.9
>> Beta testers wanted for 3.2.0.3
>>
Received on Wed Nov 10 2010 - 21:48:48 MST