On 29.06.2011 13:47, Amos Jeffries wrote: > On 29/06/11 21:59, Andre Lorenz wrote: >> Hello together, >> >> i have squid and squish on my debian box installed. >> now i would like instead of blocking internet limiting the bandwidth for >> users who are over the limit. >> >> dropping the internet after reaching the limit works fine but, not >> redirecting the users to the right delay pools >> >> >> related parts from my config >> >> ..... >> acl SQUISHLOC dst 192.168.2.70 >> acl SQUISHED1 proxy_auth -i "/etc/squid/squished" >> ##acl SQUISHED2 src "/etc/squid/squished" >> acl SQUISHED3 src "/etc/squid/squished" >> .... >> >> delay_class 1 2 >> delay_class 2 2 >> delay_parameters 1 -1/-1 -1/128000 >> delay_parameters 2 128000/64000 128000/64000 >> delay_access 2 allow testuser SQUISHED3 >> delay_access 2 deny uploader otaku localnet >> delay_access 1 allow testuser localnet >> delay_access 1 deny uploader otaku testuser SQUISHED3 >> >> any ideas ? >> i already read a lot of howtos, documentation, ..... >> >> thanks in advance >> Andre >> > > > delay_access is a "fast" group access control and will not wait fro > missing values like user credentials. You may need these at the top of > your http_access list above the first "allow" line. > > http_access allow SQUISHED3 testuser !all > http_access allow localnet testuser !all > > That tries to makes sure the values needed by delay_access allow lines > are all there. > > > Amos Hello, thanks for your answer. i tried this, inside the cache.log i can see aclMatch, but the users won't be redirected to the delay-pool. is there an debug-option to see if the delay-pool will be addressed ? andre
