{"id":141,"date":"2017-10-09T09:23:00","date_gmt":"2017-10-09T09:23:00","guid":{"rendered":"https:\/\/linuxadmin.melberi.com\/uncategorized\/squid-delay-pools-howto"},"modified":"2017-10-09T12:36:45","modified_gmt":"2017-10-09T12:36:45","slug":"squid-delay-pools-howto","status":"publish","type":"post","link":"https:\/\/www.melberi.com\/linuxadmin\/squid\/squid-delay-pools-howto","title":{"rendered":"Squid delay Pools – Per User IP Browser Window and Bandwidth Limit"},"content":{"rendered":"

How to configure squid delay Pools with Per User, Per IP, Browser, Window based Restriction, bandwidth Management, YouTube Streaming, Upload, Bucket<\/p>\n

\n

Squid delay pools Configuration Examples
\n<\/b><\/u><\/h2>\n

User based bandwidth Restriction, browser window based limit Examples.<\/p>\n

Delay pools are used for limiting the bandwidth of web traffic. We can restrict bandwidth based on source ip address, destination ip address, source domain, and destination domain.<\/p>\n

1) URL, keyword based bandwidth restriction <\/b><\/u><\/h3>\n

This will limit the bandwidth for the following keywords video.domain.com mail cricket<\/p>\n

acl group1 url_regex -i video.domain.com mail cricke<\/b><\/div>\n
delay_pools 1
\ndelay_class 1 1<\/b>
\n# 256 Kbit\/s fill rate, 1024 Kbit\/s reserve
\ndelay_parameters 1 32000\/128000
\ndelay_access 1 allow group1<\/b><\/div>\n

2) IP Based Restriction<\/b><\/u><\/h3>\n

Below configuration will restrict bandwidth for the ip range 10.5.1.1-10.5.1.255 and allow full bandwidth for the rest of all
\n<\/b><\/p>\n

acl ipgroup src 10.5.1.1-10.5.1.255\/32<\/b><\/div>\n
delay_pools 1
\ndelay_class 1 1<\/b>
\n<\/b># 256 Kbit\/s fill rate, 1024 Kbit\/s reserve
\ndelay_parameters 1 32000\/128000
\ndelay_access 1 allow ipgroup<\/b><\/div>\n
delay_access 1 deny all<\/b><\/div>\n

3) User group based restriction<\/b><\/u><\/h3>\n

Restrict bandwidth for user1,2,3
\n<\/b><\/p>\n

acl restuser proxy_auth user1 user2 user2<\/b><\/div>\n
delay_pools 1
\ndelay_class 1 1<\/b>
\n<\/b># 256 Kbit\/s fill rate, 1024 Kbit\/s reserve
\ndelay_parameters 1 32000\/128000
\ndelay_access 1 allow<\/b> restuser <\/b>\u00a0<\/b><\/div>\n
delay_access 1 deny all<\/b><\/div>\n

4)time based bandwidth limit<\/b><\/u><\/h3>\n

For time based bandwidth limiting, use the below acl
\nacl Night_time time SMTWHFA 20:00-24:00
\nacl Morning_time time SMTWHFA 00:00-08:30<\/p>\n

Delay Class<\/b><\/u><\/h3>\n

Class of the delay pool used is defined using this tag. There must be exactly one delay_class line for each delay pool. There are five categories of delay classes.<\/p>\n

class 1\u00a0\u00a0 \u00a0 <\/b>Everything is limited by a single aggregate bucket.
\nclass 2\u00a0\u00a0 \u00a0 <\/b>Everything is limited by a single aggregate bucket as well as an “individual” bucket chosen from bits 25 through 32 of the IP address.
\nclass 3\u00a0 <\/b>Everything is limited by a single aggregate bucket as well as a “network” bucket chosen from bits 17 through 24 of the IP address and a “individual” bucket chosen from bits 17 through 32 of the IP address.
\nclass 4<\/b>\u00a0 Everything in a class 3 delay pool, with an additional limit on a per user basis. This only takes effect if the username is established in advance – by forcing authentication in your http_access rules.
\nclass 5<\/b>\u00a0 Requests are grouped according their tag<\/p>\n

5) Limiting bandwidth usage both overall and per-user <\/b><\/u><\/h3>\n
acl all src all
\ndelay_pool_count 1
\ndelay_class 1 2 # delay class2<\/b><\/div>\n

#overall speed(1MB=1000\/8*1000=125000) and the per-IP speed(25k)
\ndelay_parameters 1 125000\/125000 25000\/25000
\ndelay_access 1 allow all<\/b><\/p>\n

<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

How to configure squid delay Pools with Per User, Per IP, Browser, Window based Restriction, bandwidth Management, YouTube Streaming, Upload, Bucket Squid delay pools Configuration Examples User based bandwidth Restriction,… Read more »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[84],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/posts\/141"}],"collection":[{"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/comments?post=141"}],"version-history":[{"count":4,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/posts\/141\/revisions"}],"predecessor-version":[{"id":595,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/posts\/141\/revisions\/595"}],"wp:attachment":[{"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/media?parent=141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/categories?post=141"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.melberi.com\/linuxadmin\/wp-json\/wp\/v2\/tags?post=141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}