why don't you try give your users a larger pool. here i have a 1mb link,
so i created pools of 10mega bytes with the regen rate of 20 kilobytes/s
if anyone try to download anything bigger than 10MB, it will slow down
to only 20Kb/s (180kbps), but the web browsing is great.
Chris Robertson escreveu:
RoLaNd RoLaNd wrote:
Hello,
i just configured two delay pools.
acl limitedto8 src 192.168.75.0/255.255.255.0
acl mySubnet url_regex -i 192.168.75
url_regex? Really? Why not a dstdom_regex? Furthermore, why are you
specifying that the match should be made without regards to character
case, when there are no alpha characters in the pattern?
delay_pools 2
delay_class 1 2
delay_parameters 1 -1/-1 -1/-1
So why do you have a delay pool, if it's not delaying the traffic? Is
it in the interest of NOT delaying traffic with 192.168.75 in the URL*?
#magic_words1: 192.168 we have set before
delay_access 1 allow mySubnet
delay_class 2 3
delay_access 2 allow limitedto8
delay_access 2 allow limitedto8 !mySubnet
would perform the same function.
delay_access 2 deny all
delay_parameters 2 64000/64000 -1/-1 8000/64000
such config works great for downloads as they're limited and so on..
though browsing is understandably slow..
is there a way i could give a burst for new http sessions so a page
could open faster?
You already are. Individuals are given a 512kbit initial bucket and a
64kbit/sec "pipe". The first 512kbit is only limited by the aggregate.
Chris
*using a regex, and not escaping the wild character (.) means that
192Q168!72 will be a match.
--
*Leonardo de Souza Carneiro*
*Veltrac - Tecnologia em Logística.*
lscarneiro@xxxxxxxxxxxxxx <mailto:lscarneiro@xxxxxxxxxxxxxx>
http://www.veltrac.com.br <http://www.veltrac.com.br/>
/Fone Com.: (43)2105-5601/
/Av. Higienópolis 1601 Ed. Eurocenter Sl. 803/
/Londrina- PR/
/Cep: 86015-010/
